source,file,name_ncsa,name_rfars,label,Definition,Additional Information,value,value_label,2014,2015,2016,2017,2018,2019,2020,2021,2022,2023
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,accident,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,accident,VE_TOTAL,ve_total,Number of Vehicle Forms Submitted,This data element is the number of contact motor vehicles that the officer reported on the police crash report as a unit involved in the crash.,This number represents all of the motor vehicles in the crash. This includes the vehicles in- transport that are in the Vehicle data file and the vehicles not in-transport that are in the Parkwork data file (previously Vehnit). This data element only appears in the Accident data file. Note: The Parkwork data file replaced the Vehnit data file in 2010. The Vehnit data file does not exist prior to 2005.,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,accident,VE_FORMS,ve_forms,Number of Vehicle Forms Submitted for MV In Transport,This data element is a count of the number of motor vehicles in-transport involved in the crash. Legally parked vehicles are not included.,"This data element is derived as the count of all vehicles in the crash where “Unit Type” = 1. It is the number of records in the Vehicle data file. It is unlikely that the number of vehicles involved in the crash is greater than the Number of Vehicle Forms plus two. 1975-1981: In the event of a hit-and-run crash, if the vehicle information was not known, then no vehicle form was filled out. Likewise, if no information was known on the person level, usually the driver of the unknown vehicle, then a Person Level form was not filled out. The result is that the number of unknowns is much smaller for this time period than 1982 and later. Example: From 1975 to 1980 there were 30 to 40 drivers coded with unknown sex— approximately 0.05 percent of all drivers involved in fatal crashes. In 1981 the number of drivers with unknown sex rose to over 300—approximately 0.5 percent of all drivers involved in fatal crashes. 1982-Later: In the case of a hit-and-run crash, a Vehicle-Driver form and a Person Level form for the driver are filled out. When the information about the vehicle driver or person is not known—which is often the case with hit-and-runs—the values are coded as unknown. Example: Between 1982 and 1994 the number of drivers coded with unknown sex fluctuated between 700 and 1,000—approximately 1.5 percent of all drivers involved in fatal crashes. Of the 768 people in the 1994 Annual Report file, all were drivers, and 90 percent of them were involved in hit-and-run crashes. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PVE_FORMS.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,accident,PVH_INVL,pvh_invl,Number of Parked/Working Vehicles,This data element is a count of the number of parked and working vehicles involved in the crash.,"This data element is calculated as the count of all vehicles in the crash where “Unit Type” is in (2, 3, or 4). It is the number of records in the Parkwork data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,accident,PEDS,peds,Number of Forms Submitted for Persons Not in Motor Vehicles,"This data element is the number of Person Forms (Not a Motor Vehicle Occupant) that are applicable to this case (i.e., non-occupants).","This represents the number of forms created for people not in motor vehicles. Prior to 2020 it is the number of people in the crash where “Person Type” is in (4, 5, 6, 7, 8, 10, or 19). Starting in 2020 the attributes are in (4, 5, 6, 7, 10, 11, 12, 13, or 19). Note: People where “Person Type” = 3 (Occupant of a Motor Vehicle Not In-Transport) are not included in this data element but are counted in C3A below.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,accident,PERNOTMVIT,pernotmvit,Number of Persons Not in Motor Vehicles In-Transport,"This data element is a count of the number of non-motorists in the crash. A non-motorist is defined as a pedestrian, a cyclist, an occupant of a motor vehicle not in-transport, a person riding a horse, an occupant of an animal drawn conveyance, person associated with non-motorist conveyance (e.g., baby carriage, skateboard, wheelchair), or an other non-motorist (e.g., person outside a trafficway, person in a house).","Prior to 2020 this data element is calculated as the count of all people in the crash where “Person Type” is in (3, 4, 5, 6, 7, 8, 10, or 19). Starting in 2020 the attributes are in (3, 4, 5, 6, 7, 10, 11, 12, 13, or 19).",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,accident,PERMVIT,permvit,Number of Persons in Motor Vehicles In-Transport,"This data element is a count of the number of motorists in the crash. A motorist is a driver, passenger, or unknown occupant type of a motor vehicle in-transport.","This data element is derived as the count of all people in the crash where “Person Type” is in (1, 2, or 9). Note: People where “Person Type” = 3 (Occupant of a Motor Vehicle Not In-Transport) are not included in this data element but are counted in C5 above.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,accident,PERSONS,persons,Number of MV Occupant,"This data element is a count of the number of Person Level (Motor Vehicle Occupant) Forms that are applicable to this case (i.e., occupants).","This represents the number of forms created for people in motor vehicles. It is the count of all people where “Person Type” is in (1, 2, 3, or 9). Before 2003 the policy was not to submit a Person Level form for occupants of van-based buses. Since 2003 a person level form has been submitted for all occupants of van-based vehicles, including van-based buses. 1975-1981: In the event of a hit-and-run crash, if the vehicle information was not known, then no vehicle form was filled out. Likewise, if no information was known on the person level, usually the driver of the unknown vehicle, then a Person Level form was not filled out. The result is that the number of unknowns is much smaller for this time period than 1982 and later. Example: From 1975 to 1980 there were 30 to 40 drivers coded with unknown sex, approximately 0.05 percent of all drivers involved in fatal crashes. In 1981 the number of drivers with unknown sex rose to over 300—approximately 0.5 percent of all drivers involved in fatal crashes. 1982-Later: In the case of a hit-and-run crash, a Vehicle Driver form and a Person Level form for the driver are filled out. When the information about the vehicle-driver or person is not known—which is often the case with hit-and-runs—the values are coded as unknown. Example: Between 1982 and 1994 the number of drivers coded with unknown sex fluctuated between 700 and 1,000—approximately 1.5 percent of all drivers involved in fatal crashes. Of the 768 people in the 1994 Annual Report file, all were drivers, and 90 percent of them were involved in hit-and-run crashes.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,accident,COUNTY,county,County,This data element records the location of the unstabilized event with regard to the County. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,GSA geographical codes are somewhat stable. Occasionally one code will be divided into two codes. This data element also appears in the Person data file.,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,accident,CITY,city,City,This data element records the location of the unstabilized event with regard to the City. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,GSA geographical codes are somewhat stable. Occasionally one code will be divided into two codes.,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,1,1,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,2,2,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,3,3,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,4,4,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,5,5,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,6,6,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,7,7,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,8,8,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,9,9,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,10,10,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,11,11,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,12,12,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,13,13,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,14,14,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,15,15,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,16,16,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,17,17,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,18,18,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,19,19,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,20,20,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,21,21,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,22,22,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,23,23,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,24,24,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,25,25,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,26,26,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,27,27,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,28,28,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,29,29,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,30,30,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY,day,Crash Date (Day),This data element records the day of the month on which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.,31,31,1,1,1,1,1,1,1,1,1,1
FARS,accident,MONTH,month,Crash Date (Month),This data element records the month in which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMONTH.,1,January,1,1,1,1,1,1,1,1,1,1
FARS,accident,MONTH,month,Crash Date (Month),This data element records the month in which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMONTH.,2,February,1,1,1,1,1,1,1,1,1,1
FARS,accident,MONTH,month,Crash Date (Month),This data element records the month in which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMONTH.,3,March,1,1,1,1,1,1,1,1,1,1
FARS,accident,MONTH,month,Crash Date (Month),This data element records the month in which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMONTH.,4,April,1,1,1,1,1,1,1,1,1,1
FARS,accident,MONTH,month,Crash Date (Month),This data element records the month in which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMONTH.,5,May,1,1,1,1,1,1,1,1,1,1
FARS,accident,MONTH,month,Crash Date (Month),This data element records the month in which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMONTH.,6,June,1,1,1,1,1,1,1,1,1,1
FARS,accident,MONTH,month,Crash Date (Month),This data element records the month in which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMONTH.,7,July,1,1,1,1,1,1,1,1,1,1
FARS,accident,MONTH,month,Crash Date (Month),This data element records the month in which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMONTH.,8,August,1,1,1,1,1,1,1,1,1,1
FARS,accident,MONTH,month,Crash Date (Month),This data element records the month in which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMONTH.,9,September,1,1,1,1,1,1,1,1,1,1
FARS,accident,MONTH,month,Crash Date (Month),This data element records the month in which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMONTH.,10,October,1,1,1,1,1,1,1,1,1,1
FARS,accident,MONTH,month,Crash Date (Month),This data element records the month in which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMONTH.,11,November,1,1,1,1,1,1,1,1,1,1
FARS,accident,MONTH,month,Crash Date (Month),This data element records the month in which the crash occurred.,This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMONTH.,12,December,1,1,1,1,1,1,1,1,1,1
FARS,accident,YEAR,year,Crash Date (Year),This data element records the year in which the crash occurred.,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY_WEEK,day_week,Crash Date (Day of Week),This data element records the day of the week on which the crash occurred.,"This data element has been calculated based on the year, month, and day.",1,Sunday,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY_WEEK,day_week,Crash Date (Day of Week),This data element records the day of the week on which the crash occurred.,"This data element has been calculated based on the year, month, and day.",2,Monday,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY_WEEK,day_week,Crash Date (Day of Week),This data element records the day of the week on which the crash occurred.,"This data element has been calculated based on the year, month, and day.",3,Tuesday,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY_WEEK,day_week,Crash Date (Day of Week),This data element records the day of the week on which the crash occurred.,"This data element has been calculated based on the year, month, and day.",4,Wednesday,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY_WEEK,day_week,Crash Date (Day of Week),This data element records the day of the week on which the crash occurred.,"This data element has been calculated based on the year, month, and day.",5,Thursday,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY_WEEK,day_week,Crash Date (Day of Week),This data element records the day of the week on which the crash occurred.,"This data element has been calculated based on the year, month, and day.",6,Friday,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY_WEEK,day_week,Crash Date (Day of Week),This data element records the day of the week on which the crash occurred.,"This data element has been calculated based on the year, month, and day.",7,Saturday,1,1,1,1,1,1,1,1,1,1
FARS,accident,DAY_WEEK,day_week,Crash Date (Day of Week),This data element records the day of the week on which the crash occurred.,"This data element has been calculated based on the year, month, and day.",9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",0,0:00am-0:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",1,1:00am-1:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",2,2:00am-2:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",3,3:00am-3:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",4,4:00am-4:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",5,5:00am-5:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",6,6:00am-6:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",7,7:00am-7:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",8,8:00am-8:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",9,9:00am-9:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",10,10:00am-10:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",11,11:00am-11:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",12,12:00pm-12:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",13,1:00pm-1:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",14,2:00pm-2:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",15,3:00pm-3:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",16,4:00pm-4:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",17,5:00pm-5:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",18,6:00pm-6:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",19,7:00pm-7:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",20,8:00pm-8:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",21,9:00pm-9:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",22,10:00pm-10:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",23,11:00pm-11:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOUR,hour,Crash Time (Hour),This data element records the hour at which the crash occurred.,"All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. If you need to separate day and night, see the data element LGT_COND under the heading Light Condition. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHOUR.",99,Unknown Hours,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,0,0,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,1,1,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,2,2,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,3,3,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,4,4,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,5,5,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,6,6,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,7,7,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,8,8,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,9,9,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,10,10,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,11,11,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,12,12,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,13,13,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,14,14,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,15,15,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,16,16,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,17,17,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,18,18,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,19,19,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,20,20,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,21,21,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,22,22,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,23,23,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,24,24,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,25,25,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,26,26,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,27,27,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,28,28,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,29,29,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,30,30,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,31,31,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,32,32,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,33,33,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,34,34,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,35,35,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,36,36,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,37,37,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,38,38,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,39,39,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,40,40,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,41,41,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,42,42,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,43,43,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,44,44,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,45,45,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,46,46,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,47,47,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,48,48,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,49,49,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,50,50,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,51,51,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,52,52,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,53,53,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,54,54,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,55,55,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,56,56,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,57,57,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,58,58,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,59,59,1,1,1,1,1,1,1,1,1,1
FARS,accident,MINUTE,minute,Crash Time (Minute),This data element records the minutes after the hour at which the crash occurred.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur on a different day than the arrival of emergency medical service at the crash scene/hospital. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMINUTE.,99,Unknown Minutes,1,1,1,1,1,1,1,1,1,1
FARS,accident,NHS,nhs,National Highway System,This data element identifies whether this crash occurred on a trafficway that is part of the National Highway System.,Prior to 2015 the Data Element ID was C10.,0,This section IS NOT on the NHS,1,1,1,1,1,1,1,1,1,NA
FARS,accident,NHS,nhs,National Highway System,This data element identifies whether this crash occurred on a trafficway that is part of the National Highway System.,Prior to 2015 the Data Element ID was C10.,1,This section IS ON the NHS,1,1,1,1,1,1,1,1,1,NA
FARS,accident,NHS,nhs,National Highway System,This data element identifies whether this crash occurred on a trafficway that is part of the National Highway System.,Prior to 2015 the Data Element ID was C10.,9,Unknown if this section is on the NHS,1,1,1,1,1,1,1,1,1,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,1,Rural-Principal Arterial-Interstate,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,2,Rural-Principal Arterial-Other,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,3,Rural-Minor Arterial,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,4,Rural-Major Collector,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,5,Rural-Minor Collector,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,6,Rural-Local Road or Street,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,9,Rural-Unknown Rural,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,11,Urban-Principal Arterial-Interstate,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,12,Urban-Principal Arterial-Other Freeways or Expressways,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,13,Urban-Other Principal Arterial,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,14,Urban-Minor Arterial,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,15,Urban-Collector,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,16,Urban-Local Road or Street,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,19,Urban-Unknown Urban,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROAD_FNC,road_fnc,Roadway Function Class,This data element identifies the functional classification of the trafficway on which the crash occurred.,This data element also appears in the Person data file. This data element was discontinued in 2015.,99,Unknown,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,1,Interstate,1,1,1,1,1,1,1,1,1,1
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,2,U.S. Highway,1,1,1,1,1,1,1,1,1,1
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,3,State Highway,1,1,1,1,1,1,1,1,1,1
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,4,County Road,1,1,1,1,1,1,1,1,1,NA
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,5,Local Street - Township,1,1,1,1,1,1,1,1,1,NA
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,6,Local Street - Municipality,1,1,1,1,1,1,1,1,1,NA
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,7,Local Street - Frontage Road,1,1,1,1,1,1,1,1,1,NA
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,8,Other,1,1,1,1,1,1,1,1,1,NA
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,9,Unknown,1,1,1,1,1,1,1,1,1,NA
FARS,accident,TWAY_ID,tway_id,Trafficway Identifier (1),This data element records the trafficway on which the crash occurred.,Beginning in 2004 a second trafficway identifier was added to accommodate intersection and intersection-related crashes where the officer provides the identifier for the second trafficway. Prior to 2015 the Data Element ID was C13.,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,accident,TWAY_ID2,tway_id2,Trafficway Identifier (2),This data element records the trafficway on which the crash occurred.,Beginning in 2004 a second trafficway identifier was added to accommodate intersection and intersection-related crashes where the officer provides the identifier for the second trafficway. Prior to 2015 the Data Element ID was C13.,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,accident,MILEPT,milept,MilePoint,This data element records the milepoint nearest to the location where the crash occurred.,Five digits are always coded. EXAMPLES:,0,None,1,1,1,1,1,1,1,1,1,1
FARS,accident,MILEPT,milept,MilePoint,This data element records the milepoint nearest to the location where the crash occurred.,Five digits are always coded. EXAMPLES:,99998,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,accident,MILEPT,milept,MilePoint,This data element records the milepoint nearest to the location where the crash occurred.,Five digits are always coded. EXAMPLES:,99999,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,accident,SP_JUR,sp_jur,Special Jurisdiction,"This data element identifies if the location on the trafficway where the crash occurred qualifies as a Special Jurisdiction even though it may be patrolled by State, county or local police (e.g., all State highways running through Indian Reservations are under the jurisdiction of the Indian Reservation).",Prior to 2015 the Data Element ID was C16.,0,No Special Jurisdiction,1,1,1,1,1,1,1,1,1,1
FARS,accident,SP_JUR,sp_jur,Special Jurisdiction,"This data element identifies if the location on the trafficway where the crash occurred qualifies as a Special Jurisdiction even though it may be patrolled by State, county or local police (e.g., all State highways running through Indian Reservations are under the jurisdiction of the Indian Reservation).",Prior to 2015 the Data Element ID was C16.,1,National Park Service,1,1,1,1,1,1,1,1,1,1
FARS,accident,SP_JUR,sp_jur,Special Jurisdiction,"This data element identifies if the location on the trafficway where the crash occurred qualifies as a Special Jurisdiction even though it may be patrolled by State, county or local police (e.g., all State highways running through Indian Reservations are under the jurisdiction of the Indian Reservation).",Prior to 2015 the Data Element ID was C16.,2,Military,1,1,1,1,1,1,1,1,1,1
FARS,accident,SP_JUR,sp_jur,Special Jurisdiction,"This data element identifies if the location on the trafficway where the crash occurred qualifies as a Special Jurisdiction even though it may be patrolled by State, county or local police (e.g., all State highways running through Indian Reservations are under the jurisdiction of the Indian Reservation).",Prior to 2015 the Data Element ID was C16.,3,Indian Reservation,1,1,1,1,1,1,1,1,1,1
FARS,accident,SP_JUR,sp_jur,Special Jurisdiction,"This data element identifies if the location on the trafficway where the crash occurred qualifies as a Special Jurisdiction even though it may be patrolled by State, county or local police (e.g., all State highways running through Indian Reservations are under the jurisdiction of the Indian Reservation).",Prior to 2015 the Data Element ID was C16.,4,College/University Campus*,1,1,1,1,1,1,1,1,1,1
FARS,accident,SP_JUR,sp_jur,Special Jurisdiction,"This data element identifies if the location on the trafficway where the crash occurred qualifies as a Special Jurisdiction even though it may be patrolled by State, county or local police (e.g., all State highways running through Indian Reservations are under the jurisdiction of the Indian Reservation).",Prior to 2015 the Data Element ID was C16.,5,Other Federal Properties*,1,1,1,1,1,1,1,1,1,1
FARS,accident,SP_JUR,sp_jur,Special Jurisdiction,"This data element identifies if the location on the trafficway where the crash occurred qualifies as a Special Jurisdiction even though it may be patrolled by State, county or local police (e.g., all State highways running through Indian Reservations are under the jurisdiction of the Indian Reservation).",Prior to 2015 the Data Element ID was C16.,8,Other,1,1,1,1,1,1,1,1,1,1
FARS,accident,SP_JUR,sp_jur,Special Jurisdiction,"This data element identifies if the location on the trafficway where the crash occurred qualifies as a Special Jurisdiction even though it may be patrolled by State, county or local police (e.g., all State highways running through Indian Reservations are under the jurisdiction of the Indian Reservation).",Prior to 2015 the Data Element ID was C16.,9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",1,Rollover/Overturn,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",2,Fire/Explosion,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",3,Immersion or Partial Immersion,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",4,Gas Inhalation,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",5,Fell/Jumped from Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",6,Injured In Vehicle (Non-Collision),1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",7,Other Non-Collision,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",8,Pedestrian,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",9,Pedalcyclist,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",10,Railway Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",11,Live Animal,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",12,Motor Vehicle In-Transport,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",14,Parked Motor Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",15,Non-Motorist on Personal Conveyance,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",16,Thrown or Falling Object,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",17,Boulder,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",18,Other Object (not fixed),1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",19,Building,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",20,Impact Attenuator/Crash Cushion,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",21,Bridge Pier or Support,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",23,Bridge Rail (Includes parapet),1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",24,Guardrail Face,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",25,Concrete Traffic Barrier,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",26,Other Traffic Barrier,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",30,Utility Pole/Light Support,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",31,"Other Post, Other Pole or Other Supports",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",32,Culvert,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",33,Curb,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",34,Ditch,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",35,Embankment,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",38,Fence,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",39,Wall,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",40,Fire Hydrant,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",41,Shrubbery,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",42,Tree (Standing Only),1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",43,Other Fixed Object,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",44,"Pavement Surface Irregularity (Ruts, Potholes, Grates, etc.)",1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",45,Working Motor Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",46,Traffic Signal Support,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",48,Snow Bank,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",49,Ridden Animal or Animal Drawn Conveyance,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",50,Bridge Overhead Structure,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",51,Jackknife (harmful to this vehicle),1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",52,Guardrail End,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",53,Mail Box,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",54,"Motor Vehicle In-Transport Strikes or is Struck by Cargo, Persons or Objects Set-in-Motion from/by Another Motor Vehicle In Transport",1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",55,Motor Vehicle in Motion Outside the Trafficway,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",57,Cable Barrier,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",58,Ground,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",59,Traffic Sign Support,1,1,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",72,Cargo/Equipment Loss or Shift (harmful to this vehicle),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",73,Object Fell From Motor Vehicle In-Transport,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,MAN_COLL,man_coll,Manner of Collision,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",0,Not a Collision with Motor Vehicle In-Transport,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,MAN_COLL,man_coll,Manner of Collision,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",1,Front-to-Rear,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,MAN_COLL,man_coll,Manner of Collision,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",2,Front-to-Front,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,MAN_COLL,man_coll,Manner of Collision,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",6,Angle,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,MAN_COLL,man_coll,Manner of Collision,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",7,Sideswipe - Same Direction,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,MAN_COLL,man_coll,Manner of Collision,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",8,Sideswipe - Opposite Direction,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,MAN_COLL,man_coll,Manner of Collision,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",9,Rear-to-Side,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,MAN_COLL,man_coll,Manner of Collision,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",10,Rear-to-Rear,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,MAN_COLL,man_coll,Manner of Collision,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",11,Other,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,MAN_COLL,man_coll,Manner of Collision,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",98,Not Reported,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,MAN_COLL,man_coll,Manner of Collision,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,RELJCT1,reljct1,Relation to Junction Within Interchange Area,This data element identifies the crash’s location with respect to presence in an interchange area. The coding of this data element is done in two sub-fields (see also C20B) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20A.,0,No,1,1,1,1,1,1,1,1,1,NA
FARS,accident,RELJCT1,reljct1,Relation to Junction Within Interchange Area,This data element identifies the crash’s location with respect to presence in an interchange area. The coding of this data element is done in two sub-fields (see also C20B) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20A.,1,Yes,1,1,1,1,1,1,1,1,1,NA
FARS,accident,RELJCT1,reljct1,Relation to Junction Within Interchange Area,This data element identifies the crash’s location with respect to presence in an interchange area. The coding of this data element is done in two sub-fields (see also C20B) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20A.,8,Not Reported,1,1,1,1,1,1,1,1,1,NA
FARS,accident,RELJCT1,reljct1,Relation to Junction Within Interchange Area,This data element identifies the crash’s location with respect to presence in an interchange area. The coding of this data element is done in two sub-fields (see also C20B) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20A.,9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,1,Non-Junction,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,2,Intersection,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,3,Intersection-Related,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,4,Driveway Access,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,5,Entrance/Exit Ramp Related,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,6,Railway Grade Crossing,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,7,Crossover-Related,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,8,Driveway Access Related,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,16,Shared-Use Path Crossing,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,17,Acceleration/Deceleration Lane,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,18,Through Roadway,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,19,Other location within Interchange Area,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,20,Entrance/Exit Ramp,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,TYP_INT,typ_int,Type of Intersection,This data element identifies and allows separation of various intersection types.,Prior to 2015 the Data Element ID was C21.,1,Not an Intersection,1,1,1,1,1,1,1,1,1,1
FARS,accident,TYP_INT,typ_int,Type of Intersection,This data element identifies and allows separation of various intersection types.,Prior to 2015 the Data Element ID was C21.,2,Four-Way Intersection,1,1,1,1,1,1,1,1,1,1
FARS,accident,TYP_INT,typ_int,Type of Intersection,This data element identifies and allows separation of various intersection types.,Prior to 2015 the Data Element ID was C21.,3,T-Intersection,1,1,1,1,1,1,1,1,1,1
FARS,accident,TYP_INT,typ_int,Type of Intersection,This data element identifies and allows separation of various intersection types.,Prior to 2015 the Data Element ID was C21.,4,Y-Intersection,1,1,1,1,1,1,1,1,1,1
FARS,accident,TYP_INT,typ_int,Type of Intersection,This data element identifies and allows separation of various intersection types.,Prior to 2015 the Data Element ID was C21.,5,Traffic Circle,1,1,1,1,1,1,1,1,1,1
FARS,accident,TYP_INT,typ_int,Type of Intersection,This data element identifies and allows separation of various intersection types.,Prior to 2015 the Data Element ID was C21.,6,Roundabout,1,1,1,1,1,1,1,1,1,1
FARS,accident,TYP_INT,typ_int,Type of Intersection,This data element identifies and allows separation of various intersection types.,Prior to 2015 the Data Element ID was C21.,7,"Five Point, or More",1,1,1,1,1,1,1,1,1,1
FARS,accident,TYP_INT,typ_int,Type of Intersection,This data element identifies and allows separation of various intersection types.,Prior to 2015 the Data Element ID was C21.,10,L-Intersection,1,1,1,1,1,1,1,1,1,1
FARS,accident,TYP_INT,typ_int,Type of Intersection,This data element identifies and allows separation of various intersection types.,Prior to 2015 the Data Element ID was C21.,98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,accident,TYP_INT,typ_int,Type of Intersection,This data element identifies and allows separation of various intersection types.,Prior to 2015 the Data Element ID was C21.,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,WRK_ZONE,wrk_zone,Work Zone,"This data element identifies a motor vehicle traffic crash in which the first harmful event occurs within the boundaries of a work zone or on an approach to or exit from a work zone, resulting from an activity, behavior, or control related to the movement of the traffic units through the work zone.","This data element identifies a “Work Zone Accident” as defined in ANSI D16.1, 7th Edition. If the crash qualifies as a “Work Zone Accident” then the type of work activity is identified. Use of the codes does not imply that the crash was caused by the construction, maintenance, or work activity. The data element name was “Construction/Maintenance Zone” from 1975 to 2008. The data element name has been changed to “Work Zone” since 2009. Prior to 2015 the Data Element ID was C23.",0,None,1,1,1,1,1,1,1,1,1,1
FARS,accident,WRK_ZONE,wrk_zone,Work Zone,"This data element identifies a motor vehicle traffic crash in which the first harmful event occurs within the boundaries of a work zone or on an approach to or exit from a work zone, resulting from an activity, behavior, or control related to the movement of the traffic units through the work zone.","This data element identifies a “Work Zone Accident” as defined in ANSI D16.1, 7th Edition. If the crash qualifies as a “Work Zone Accident” then the type of work activity is identified. Use of the codes does not imply that the crash was caused by the construction, maintenance, or work activity. The data element name was “Construction/Maintenance Zone” from 1975 to 2008. The data element name has been changed to “Work Zone” since 2009. Prior to 2015 the Data Element ID was C23.",1,Construction,1,1,1,1,1,1,1,1,1,1
FARS,accident,WRK_ZONE,wrk_zone,Work Zone,"This data element identifies a motor vehicle traffic crash in which the first harmful event occurs within the boundaries of a work zone or on an approach to or exit from a work zone, resulting from an activity, behavior, or control related to the movement of the traffic units through the work zone.","This data element identifies a “Work Zone Accident” as defined in ANSI D16.1, 7th Edition. If the crash qualifies as a “Work Zone Accident” then the type of work activity is identified. Use of the codes does not imply that the crash was caused by the construction, maintenance, or work activity. The data element name was “Construction/Maintenance Zone” from 1975 to 2008. The data element name has been changed to “Work Zone” since 2009. Prior to 2015 the Data Element ID was C23.",2,Maintenance,1,1,1,1,1,1,1,1,1,1
FARS,accident,WRK_ZONE,wrk_zone,Work Zone,"This data element identifies a motor vehicle traffic crash in which the first harmful event occurs within the boundaries of a work zone or on an approach to or exit from a work zone, resulting from an activity, behavior, or control related to the movement of the traffic units through the work zone.","This data element identifies a “Work Zone Accident” as defined in ANSI D16.1, 7th Edition. If the crash qualifies as a “Work Zone Accident” then the type of work activity is identified. Use of the codes does not imply that the crash was caused by the construction, maintenance, or work activity. The data element name was “Construction/Maintenance Zone” from 1975 to 2008. The data element name has been changed to “Work Zone” since 2009. Prior to 2015 the Data Element ID was C23.",3,Utility,1,1,1,1,1,1,1,1,1,1
FARS,accident,WRK_ZONE,wrk_zone,Work Zone,"This data element identifies a motor vehicle traffic crash in which the first harmful event occurs within the boundaries of a work zone or on an approach to or exit from a work zone, resulting from an activity, behavior, or control related to the movement of the traffic units through the work zone.","This data element identifies a “Work Zone Accident” as defined in ANSI D16.1, 7th Edition. If the crash qualifies as a “Work Zone Accident” then the type of work activity is identified. Use of the codes does not imply that the crash was caused by the construction, maintenance, or work activity. The data element name was “Construction/Maintenance Zone” from 1975 to 2008. The data element name has been changed to “Work Zone” since 2009. Prior to 2015 the Data Element ID was C23.",4,"Work Zone, Type Unknown",1,1,1,1,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,1,On Roadway,1,1,1,1,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,2,On Shoulder,1,1,1,1,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,3,On Median,1,1,1,1,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,4,On Roadside,1,1,1,1,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,5,Outside Trafficway,1,1,1,1,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,6,Off Roadway-Location Unknown,1,1,1,1,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,7,In Parking Lane/Zone,1,1,1,1,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,8,Gore,1,1,1,1,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,10,Separator,1,1,1,1,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,11,Continuous Left - Turn Lane,1,1,1,1,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,LGT_COND,lgt_cond,Light Condition,This data element records the type/level of light that existed at the time of the crash as indicated in the case material.,Prior to 2015 the Data Element ID was C24.,1,Daylight,1,1,1,1,1,1,1,1,1,1
FARS,accident,LGT_COND,lgt_cond,Light Condition,This data element records the type/level of light that existed at the time of the crash as indicated in the case material.,Prior to 2015 the Data Element ID was C24.,2,Dark - Not Lighted,1,1,1,1,1,1,1,1,1,1
FARS,accident,LGT_COND,lgt_cond,Light Condition,This data element records the type/level of light that existed at the time of the crash as indicated in the case material.,Prior to 2015 the Data Element ID was C24.,3,Dark - Lighted,1,1,1,1,1,1,1,1,1,1
FARS,accident,LGT_COND,lgt_cond,Light Condition,This data element records the type/level of light that existed at the time of the crash as indicated in the case material.,Prior to 2015 the Data Element ID was C24.,4,Dawn,1,1,1,1,1,1,1,1,1,1
FARS,accident,LGT_COND,lgt_cond,Light Condition,This data element records the type/level of light that existed at the time of the crash as indicated in the case material.,Prior to 2015 the Data Element ID was C24.,5,Dusk,1,1,1,1,1,1,1,1,1,1
FARS,accident,LGT_COND,lgt_cond,Light Condition,This data element records the type/level of light that existed at the time of the crash as indicated in the case material.,Prior to 2015 the Data Element ID was C24.,6,Dark - Unknown Lighting,1,1,1,1,1,1,1,1,1,1
FARS,accident,LGT_COND,lgt_cond,Light Condition,This data element records the type/level of light that existed at the time of the crash as indicated in the case material.,Prior to 2015 the Data Element ID was C24.,7,Other,1,1,1,1,1,1,1,1,1,1
FARS,accident,LGT_COND,lgt_cond,Light Condition,This data element records the type/level of light that existed at the time of the crash as indicated in the case material.,Prior to 2015 the Data Element ID was C24.,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,accident,LGT_COND,lgt_cond,Light Condition,This data element records the type/level of light that existed at the time of the crash as indicated in the case material.,Prior to 2015 the Data Element ID was C24.,9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",0,No Additional Atmospheric Conditions,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",1,Clear,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",2,Rain,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",3,Sleet or Hail,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",4,Snow,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",5,"Fog, Smog, Smoke",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",6,Severe Crosswinds,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",7,"Blowing Sand, Soil, Dirt",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",8,Other,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",10,Cloudy,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",11,Blowing Snow,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",12,Freezing Rain or Drizzle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",98,Not Reported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",0,No Additional Atmospheric Conditions,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",1,Clear,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",2,Rain,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",3,Sleet or Hail,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",4,Snow,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",5,"Fog, Smog, Smoke",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",6,Severe Crosswinds,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",7,"Blowing Sand, Soil, Dirt",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",8,Other,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",10,Cloudy,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",11,Blowing Snow,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",12,Freezing Rain or Drizzle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",98,Not Reported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",0,No Additional Atmospheric Conditions,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",1,Clear,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",2,Rain,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",3,Sleet or Hail,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",4,Snow,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",5,"Fog, Smog, Smoke",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",6,Severe Crosswinds,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",7,"Blowing Sand, Soil, Dirt",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",8,Other,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",10,Cloudy,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",11,Blowing Snow,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",12,Freezing Rain or Drizzle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",98,Not Reported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,SCH_BUS,sch_bus,School Bus Related,"This data element identifies if a school bus, or motor vehicle functioning as a school bus, is related to the crash.","A school bus crash is (1) a motor vehicle crash in which a school bus, with or without a pupil on board, is involved directly as a contact vehicle, or (2) a motor vehicle crash or an other-road- vehicle crash in which a school bus, with or without a pupil or board, is involved indirectly as a non-contact vehicle. Prior to 2015 the Data Element ID was C26. This data element also appears on the Person data file.",0,No,1,1,1,1,1,1,1,1,1,1
FARS,accident,SCH_BUS,sch_bus,School Bus Related,"This data element identifies if a school bus, or motor vehicle functioning as a school bus, is related to the crash.","A school bus crash is (1) a motor vehicle crash in which a school bus, with or without a pupil on board, is involved directly as a contact vehicle, or (2) a motor vehicle crash or an other-road- vehicle crash in which a school bus, with or without a pupil or board, is involved indirectly as a non-contact vehicle. Prior to 2015 the Data Element ID was C26. This data element also appears on the Person data file.",1,Yes,1,1,1,1,1,1,1,1,1,1
FARS,accident,RAIL,rail,Rail Grade Crossing Identifier,This data element identifies if the crash occurred in or near a rail grade crossing.,Prior to 2015 the Data Element ID was C27.,0000000,Not Applicable,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,RAIL,rail,Rail Grade Crossing Identifier,This data element identifies if the crash occurred in or near a rail grade crossing.,Prior to 2015 the Data Element ID was C27.,9999999,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,0,0:00am-0:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,1,1:00am-1:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,2,2:00am-2:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,3,3:00am-3:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,4,4:00am-4:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,5,5:00am-5:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,6,6:00am-6:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,7,7:00am-7:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,8,8:00am-8:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,9,9:00am-9:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,10,10:00am-10:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,11,11:00am-11:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,12,12:00pm-12:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,13,1:00pm-1:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,14,2:00pm-2:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,15,3:00pm-3:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,16,4:00pm-4:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,17,5:00pm-5:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,18,6:00pm-6:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,19,7:00pm-7:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,20,8:00pm-8:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,21,9:00pm-9:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,22,10:00pm-10:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,23,11:00pm-11:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,88,Not Applicable (Not Notified),1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_HOUR,not_hour,Notification Time EMS (Hour),This data element records the hour that emergency medical service was notified.,All time is 24-hour military time. Prior to 2015 the Data Element ID was C28A.,99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,0,0,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,1,1,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,2,2,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,3,3,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,4,4,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,5,5,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,6,6,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,7,7,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,8,8,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,9,9,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,10,10,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,11,11,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,12,12,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,13,13,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,14,14,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,15,15,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,16,16,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,17,17,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,18,18,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,19,19,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,20,20,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,21,21,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,22,22,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,23,23,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,24,24,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,25,25,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,26,26,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,27,27,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,28,28,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,29,29,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,30,30,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,31,31,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,32,32,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,33,33,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,34,34,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,35,35,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,36,36,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,37,37,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,38,38,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,39,39,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,40,40,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,41,41,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,42,42,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,43,43,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,44,44,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,45,45,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,46,46,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,47,47,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,48,48,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,49,49,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,50,50,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,51,51,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,52,52,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,53,53,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,54,54,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,55,55,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,56,56,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,57,57,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,58,58,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,59,59,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,88,Not Applicable (Not Notified),1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,98,Unknown if Notified,1,1,1,1,1,1,1,1,1,1
FARS,accident,NOT_MIN,not_min,Notification Time EMS (Min),This data element records the minutes after the hour that emergency medical service was notified.,Prior to 2015 the Data Element ID was C28B.,99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,0,0:00am-0:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,1,1:00am-1:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,2,2:00am-2:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,3,3:00am-3:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,4,4:00am-4:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,5,5:00am-5:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,6,6:00am-6:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,7,7:00am-7:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,8,8:00am-8:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,9,9:00am-9:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,10,10:00am-10:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,11,11:00am-11:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,12,12:00pm-12:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,13,1:00pm-1:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,14,2:00pm-2:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,15,3:00pm-3:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,16,4:00pm-4:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,17,5:00pm-5:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,18,6:00pm-6:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,19,7:00pm-7:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,20,8:00pm-8:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,21,9:00pm-9:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,22,10:00pm-10:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,23,11:00pm-11:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,88,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_HOUR,arr_hour,Arrival Time EMS (Hour),This data element records the hour that emergency medical service arrived on the crash scene.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29A.,99,Unknown EMS Scene Arrival Hour,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,0,0,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,1,1,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,2,2,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,3,3,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,4,4,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,5,5,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,6,6,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,7,7,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,8,8,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,9,9,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,10,10,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,11,11,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,12,12,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,13,13,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,14,14,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,15,15,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,16,16,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,17,17,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,18,18,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,19,19,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,20,20,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,21,21,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,22,22,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,23,23,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,24,24,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,25,25,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,26,26,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,27,27,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,28,28,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,29,29,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,30,30,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,31,31,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,32,32,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,33,33,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,34,34,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,35,35,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,36,36,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,37,37,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,38,38,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,39,39,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,40,40,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,41,41,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,42,42,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,43,43,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,44,44,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,45,45,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,46,46,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,47,47,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,48,48,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,49,49,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,50,50,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,51,51,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,52,52,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,53,53,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,54,54,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,55,55,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,56,56,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,57,57,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,58,58,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,59,59,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,88,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,97,Officially Cancelled,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,98,Unknown if Arrived,1,1,1,1,1,1,1,1,1,1
FARS,accident,ARR_MIN,arr_min,Arrival Time EMS (Min),This data element records the minutes after the hour that emergency medical service arrived on the crash scene.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C29B.,99,Unknown EMS Scene Arrival Minutes,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,0,0:00am-0:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,1,1:00am-1:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,2,2:00am-2:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,3,3:00am-3:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,4,4:00am-4:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,5,5:00am-5:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,6,6:00am-6:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,7,7:00am-7:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,8,8:00am-8:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,9,9:00am-9:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,10,10:00am-10:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,11,11:00am-11:59am,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,12,12:00pm-12:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,13,1:00pm-1:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,14,2:00pm-2:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,15,3:00pm-3:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,16,4:00pm-4:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,17,5:00pm-5:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,18,6:00pm-6:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,19,7:00pm-7:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,20,8:00pm-8:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,21,9:00pm-9:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,22,10:00pm-10:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,23,11:00pm-11:59pm,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,88,Not Applicable (Not Transported),1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_HR,hosp_hr,EMS Time at Hospital (Hour),This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,All time is 24-hour military time. The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30A.,99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,0,0,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,1,1,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,2,2,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,3,3,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,4,4,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,5,5,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,6,6,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,7,7,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,8,8,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,9,9,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,10,10,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,11,11,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,12,12,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,13,13,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,14,14,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,15,15,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,16,16,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,17,17,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,18,18,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,19,19,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,20,20,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,21,21,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,22,22,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,23,23,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,24,24,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,25,25,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,26,26,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,27,27,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,28,28,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,29,29,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,30,30,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,31,31,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,32,32,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,33,33,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,34,34,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,35,35,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,36,36,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,37,37,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,38,38,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,39,39,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,40,40,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,41,41,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,42,42,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,43,43,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,44,44,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,45,45,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,46,46,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,47,47,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,48,48,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,49,49,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,50,50,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,51,51,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,52,52,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,53,53,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,54,54,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,55,55,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,56,56,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,57,57,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,58,58,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,59,59,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,88,Not Applicable (Not Transported),1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,96,Terminated Transport,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,97,Officially Canceled,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,98,Unknown if Transported,1,1,1,1,1,1,1,1,1,1
FARS,accident,HOSP_MN,hosp_mn,EMS Time at Hospital (Min),This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.,The time of the crash/arrival of the emergency medical service can occur in a different day than the arrival of emergency medical service at the crash scene/hospital. Prior to 2015 the Data Element ID was C30B.,99,Unknown EMS Hospital Arrival Time,1,1,1,1,1,1,1,1,1,1
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",1,"Inadequate Warning of Exits, Lanes Narrowing, Traffic Controls, etc.",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",2,Shoulder Design or Condition,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",3,Other Maintenance or Construction-Created Condition,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",4,No or Obscured Pavement Marking,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",5,Surface Under Water,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",6,"Inadequate Construction or Poor Design of Roadway,Bridge, etc.",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",7,"Surface Washed Out(caved-in, road slippage)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",13,Aggressive Driving / Road Rage by Non-contact Vehicle Driver,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",14,"Motor Vehicle struck by falling cargo,or something that came loose from or something that was set in motion by a vehicle",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",15,"Non-occupant struck by falling cargo, or something that came loose from, or something that was set in motion by a vehicle",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",16,Non-occupant struck vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",17,Vehicle set-in-motion by non-driver,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",18,Date of Crash and Date of EMS Notification were not the same day,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",19,Recent/Previous Crash scene Nearby,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",20,Police Pursuit Involved,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",21,Within Designated School Zone,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",22,Speed Limit is a Statutory Limit as Recorded or was determined as this state`s `basic rule`,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",23,Indication of a Stalled/Disabled Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",24,Unstabalized Situation Began and All Harmful Events Occurred Off of the Roadway,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",25,Toll Booth/Plaza Related,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",26,Backup Due to Prior Non-Recurring Incident,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",27,Backup Due to Prior Crash,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",28,Backup Due to Regular Congestion,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",1,"Inadequate Warning of Exits, Lanes Narrowing, Traffic Controls, etc.",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",2,Shoulder Design or Condition,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",3,Other Maintenance or Construction-Created Condition,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",4,No or Obscured Pavement Marking,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",5,Surface Under Water,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",6,"Inadequate Construction or Poor Design of Roadway,Bridge, etc.",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",7,"Surface Washed Out(caved-in, road slippage)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",13,Aggressive Driving / Road Rage by Non-contact Vehicle Driver,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",14,"Motor Vehicle struck by falling cargo,or something that came loose from or something that was set in motion by a vehicle",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",15,"Non-occupant struck by falling cargo, or something that came loose from, or something that was set in motion by a vehicle",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",16,Non-occupant struck vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",17,Vehicle set-in-motion by non-driver,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",18,Date of Crash and Date of EMS Notification were not the same day,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",19,Recent/Previous Crash scene Nearby,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",20,Police Pursuit Involved,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",21,Within Designated School Zone,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",22,Speed Limit is a Statutory Limit as Recorded or was determined as this state`s `basic rule`,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",23,Indication of a Stalled/Disabled Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",24,Unstabalized Situation Began and All Harmful Events Occurred Off of the Roadway,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",25,Toll Booth/Plaza Related,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",26,Backup Due to Prior Non-Recurring Incident,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",27,Backup Due to Prior Crash,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",28,Backup Due to Regular Congestion,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",1,"Inadequate Warning of Exits, Lanes Narrowing, Traffic Controls, etc.",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",2,Shoulder Design or Condition,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",3,Other Maintenance or Construction-Created Condition,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",4,No or Obscured Pavement Marking,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",5,Surface Under Water,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",6,"Inadequate Construction or Poor Design of Roadway,Bridge, etc.",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",7,"Surface Washed Out(caved-in, road slippage)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",13,Aggressive Driving / Road Rage by Non-contact Vehicle Driver,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",14,"Motor Vehicle struck by falling cargo,or something that came loose from or something that was set in motion by a vehicle",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",15,"Non-occupant struck by falling cargo, or something that came loose from, or something that was set in motion by a vehicle",1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",16,Non-occupant struck vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",17,Vehicle set-in-motion by non-driver,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",18,Date of Crash and Date of EMS Notification were not the same day,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",19,Recent/Previous Crash scene Nearby,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",20,Police Pursuit Involved,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",21,Within Designated School Zone,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",22,Speed Limit is a Statutory Limit as Recorded or was determined as this state`s `basic rule`,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",23,Indication of a Stalled/Disabled Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",24,Unstabalized Situation Began and All Harmful Events Occurred Off of the Roadway,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",25,Toll Booth/Plaza Related,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",26,Backup Due to Prior Non-Recurring Incident,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",27,Backup Due to Prior Crash,1,1,1,1,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",28,Backup Due to Regular Congestion,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,FATALS,fatals,Fatalities,This data element records the number of fatally injured people in the crash.,The data element is derived by counting all people with “Injury Severity” of 4 in the crash. The data element “Fatalities in Vehicle” in the Vehicle data file provides the number of deaths in a vehicle.,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,accident,DRUNK_DR,drunk_dr,Drunk Drivers,This data element records the number of drinking drivers involved in the crash.,"This data element is derived from data elements in the Person data files. If the blood alcohol concentration (BAC) is positive, or if the police reported alcohol involvement, then the driver is counted as a drinking driver. A driver who is charged with an alcohol violation by itself does not have the driver counted as a drinking driver. In the early years of FARS, especially 1975 and 1976, the alcohol data must be used with care. In these 2 years no drinking drivers were identified for North Dakota. In 1975 and 1976 Alabama, Mississippi, New Mexico, North Carolina, Texas, and West Virginia have a reported drinking driver rate for fatal crashes of less than 5 percent. In 1979 the data from these States reports a drinking driver rate for fatal crashes between 18.5 percent and 43 percent. From 1999 through 2007 this data element was incorrectly derived for all Person types rather than based on Drivers only. Beginning with the 2008 Final FARS data file, this element has been derived for Drivers only. For consistency, the number of drinking drivers should be derived manually when trying to obtain this data from 1999 to 2007 – refer to the DRUNK_DR Logic Derivation for “1975-1998 and 2008-2014” in Appendix B: Rules for Derived Data Elements. Prior to 2015 this data element’s name was “Drunk Drivers.” The former data element name implied that the individuals were drunk; however, this data element actually captures those individuals whom the police reported alcohol involvement OR who tested positive for alcohol (i.e., their blood alcohol concentrations were .01 g/dL or greater prior to 2015 or .001 g/dL or greater for 2015 and later). NOTES:    •   Alcohol data is often missing. For that reason, this data element may undercount the        actual number of drinking drivers.    •   The change to a three-digit BAC in 2015 means that a BAC of .001 or greater qualifies as        a drinking driver, whereas prior to 2015 a BAC of .01 or greater qualified as a drinking        driver. This may have ramifications for trend analyses. This data element, formerly C100, was discontinued after 2015.",NA,(Self-evident),1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",0,None,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",1,01,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",2,02,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",3,03,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",4,04,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",5,05,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",6,06,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",7,07,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",8,08,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",9,09,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",10,10,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",11,11,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",12,12,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",13,13,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",14,14,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",15,15,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",16,16,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",17,17,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",18,18,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",19,19,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",20,20,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",21,21,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",22,22,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",23,23,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",24,24,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",25,25,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",26,26,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",27,27,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",28,28,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",29,29,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",30,30,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",31,31,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",32,32,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",33,33,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",34,34,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",35,35,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",36,36,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",37,37,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",38,38,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",39,39,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",40,40,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",41,41,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",42,42,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",43,43,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",44,44,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",45,45,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",46,46,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",47,47,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",48,48,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",49,49,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",50,50,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",51,51,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",52,52,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",53,53,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",54,54,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",55,55,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",56,56,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",57,57,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",58,58,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",59,59,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",60,60,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",61,61,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",62,62,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",63,63,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",64,64,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",65,65,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",66,66,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",67,67,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",68,68,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",69,69,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",70,70,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",71,71,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",72,72,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",73,73,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",74,74,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",75,75,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",76,76,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",77,77,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",78,78,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",79,79,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",80,80,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",81,81,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",82,82,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",83,83,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",84,84,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",85,85,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",86,86,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",87,87,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",88,88,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",89,89,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",90,90,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",91,91,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",92,92,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",93,93,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",94,94,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",95,95,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",96,Ninety-Six or more,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,UNITTYPE,unittype,Unit Type,This data element identifies the type of unit that applies to this motor vehicle at the time it became an involved vehicle in the crash and was reported as a unit on the police crash report.,"This data element also appears in the Parkwork data file as PTYPE. The valid attributes for PTYPE are:        2        Motor Vehicle Not In-Transport Within the Trafficway        3        Motor Vehicle Not In-Transport Outside the Trafficway        4        Working Motor Vehicle (Highway Construction, Maintenance, Utility Only) This data element also appears in the Vehicle data file as UNITTYPE. The only valid attribute for UNITTYPE is 1 (Motor Vehicle In-Transport [Inside or Outside the Trafficway]).",1,Motor Vehicle In-Transport (Inside or Outside the Trafficway),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,UNITTYPE,unittype,Unit Type,This data element identifies the type of unit that applies to this motor vehicle at the time it became an involved vehicle in the crash and was reported as a unit on the police crash report.,"This data element also appears in the Parkwork data file as PTYPE. The valid attributes for PTYPE are:        2        Motor Vehicle Not In-Transport Within the Trafficway        3        Motor Vehicle Not In-Transport Outside the Trafficway        4        Working Motor Vehicle (Highway Construction, Maintenance, Utility Only) This data element also appears in the Vehicle data file as UNITTYPE. The only valid attribute for UNITTYPE is 1 (Motor Vehicle In-Transport [Inside or Outside the Trafficway]).",2,Motor Vehicle Not In-Transport Within the Trafficway,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,UNITTYPE,unittype,Unit Type,This data element identifies the type of unit that applies to this motor vehicle at the time it became an involved vehicle in the crash and was reported as a unit on the police crash report.,"This data element also appears in the Parkwork data file as PTYPE. The valid attributes for PTYPE are:        2        Motor Vehicle Not In-Transport Within the Trafficway        3        Motor Vehicle Not In-Transport Outside the Trafficway        4        Working Motor Vehicle (Highway Construction, Maintenance, Utility Only) This data element also appears in the Vehicle data file as UNITTYPE. The only valid attribute for UNITTYPE is 1 (Motor Vehicle In-Transport [Inside or Outside the Trafficway]).",3,Motor Vehicle Not In-Transport Outside the Trafficway,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,UNITTYPE,unittype,Unit Type,This data element identifies the type of unit that applies to this motor vehicle at the time it became an involved vehicle in the crash and was reported as a unit on the police crash report.,"This data element also appears in the Parkwork data file as PTYPE. The valid attributes for PTYPE are:        2        Motor Vehicle Not In-Transport Within the Trafficway        3        Motor Vehicle Not In-Transport Outside the Trafficway        4        Working Motor Vehicle (Highway Construction, Maintenance, Utility Only) This data element also appears in the Vehicle data file as UNITTYPE. The only valid attribute for UNITTYPE is 1 (Motor Vehicle In-Transport [Inside or Outside the Trafficway]).",4,"Working Motor Vehicle (highway construction, maintenance, utility only)",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HIT_RUN,hit_run,Hit and Run,"This data element identifies whether this vehicle was a contact vehicle in the crash that did not stop to render aid (this can include drivers who flee the scene on foot). Hit-and-run is coded when a motor vehicle in-transport or its driver departs from the scene; vehicles not in-transport are excluded. It does not matter whether the hit-and-run vehicle was striking or struck. This data element identifies whether this vehicle was a contact vehicle in the crash that did not stop to render aid (this can include drivers who flee the scene on foot). Hit-and-run is coded when a motor vehicle in-transport, or its driver, departs from the scene; motor vehicles not in- transport are excluded. It does not matter whether the hit-and-run vehicle was striking or struck.","From 1975 to 1981 if no information was known about the Hit-and-Run vehicle and/or driver, the vehicle form and/or driver form were not filled out and were not counted as unknown. Starting in 1982 both a vehicle and a driver form were filled out and the data were identified as unknown. This is why, for example, there were approximately only 20 to 40 drivers with unknown sex listed in the FARS data file from 1975 to 1981 and 700 to 1,000 drivers with unknown sex from 1982 on. In 2009 this data element was no longer collected at the Accident level and is now collected at the Vehicle level. From 1975 to 1981 if no information was known about the Hit-and-Run vehicle and/or driver, the vehicle form and/or driver form were not filled out and were not counted as unknown. Starting in 1982 both a vehicle and a driver form were filled out and the data were identified as unknown. This is why, for example, there were approximately only 20 to 40 drivers with unknown sex listed in the FARS data file from 1975 to 1981 and more than 700 drivers with unknown sex from 1982 on. This data element was removed from Accident data file in 2009. This data element also appears in the Parkwork data file as PHIT_RUN.",0,No,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HIT_RUN,hit_run,Hit and Run,"This data element identifies whether this vehicle was a contact vehicle in the crash that did not stop to render aid (this can include drivers who flee the scene on foot). Hit-and-run is coded when a motor vehicle in-transport or its driver departs from the scene; vehicles not in-transport are excluded. It does not matter whether the hit-and-run vehicle was striking or struck. This data element identifies whether this vehicle was a contact vehicle in the crash that did not stop to render aid (this can include drivers who flee the scene on foot). Hit-and-run is coded when a motor vehicle in-transport, or its driver, departs from the scene; motor vehicles not in- transport are excluded. It does not matter whether the hit-and-run vehicle was striking or struck.","From 1975 to 1981 if no information was known about the Hit-and-Run vehicle and/or driver, the vehicle form and/or driver form were not filled out and were not counted as unknown. Starting in 1982 both a vehicle and a driver form were filled out and the data were identified as unknown. This is why, for example, there were approximately only 20 to 40 drivers with unknown sex listed in the FARS data file from 1975 to 1981 and 700 to 1,000 drivers with unknown sex from 1982 on. In 2009 this data element was no longer collected at the Accident level and is now collected at the Vehicle level. From 1975 to 1981 if no information was known about the Hit-and-Run vehicle and/or driver, the vehicle form and/or driver form were not filled out and were not counted as unknown. Starting in 1982 both a vehicle and a driver form were filled out and the data were identified as unknown. This is why, for example, there were approximately only 20 to 40 drivers with unknown sex listed in the FARS data file from 1975 to 1981 and more than 700 drivers with unknown sex from 1982 on. This data element was removed from Accident data file in 2009. This data element also appears in the Parkwork data file as PHIT_RUN.",1,Yes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HIT_RUN,hit_run,Hit and Run,"This data element identifies whether this vehicle was a contact vehicle in the crash that did not stop to render aid (this can include drivers who flee the scene on foot). Hit-and-run is coded when a motor vehicle in-transport or its driver departs from the scene; vehicles not in-transport are excluded. It does not matter whether the hit-and-run vehicle was striking or struck. This data element identifies whether this vehicle was a contact vehicle in the crash that did not stop to render aid (this can include drivers who flee the scene on foot). Hit-and-run is coded when a motor vehicle in-transport, or its driver, departs from the scene; motor vehicles not in- transport are excluded. It does not matter whether the hit-and-run vehicle was striking or struck.","From 1975 to 1981 if no information was known about the Hit-and-Run vehicle and/or driver, the vehicle form and/or driver form were not filled out and were not counted as unknown. Starting in 1982 both a vehicle and a driver form were filled out and the data were identified as unknown. This is why, for example, there were approximately only 20 to 40 drivers with unknown sex listed in the FARS data file from 1975 to 1981 and 700 to 1,000 drivers with unknown sex from 1982 on. In 2009 this data element was no longer collected at the Accident level and is now collected at the Vehicle level. From 1975 to 1981 if no information was known about the Hit-and-Run vehicle and/or driver, the vehicle form and/or driver form were not filled out and were not counted as unknown. Starting in 1982 both a vehicle and a driver form were filled out and the data were identified as unknown. This is why, for example, there were approximately only 20 to 40 drivers with unknown sex listed in the FARS data file from 1975 to 1981 and more than 700 drivers with unknown sex from 1982 on. This data element was removed from Accident data file in 2009. This data element also appears in the Parkwork data file as PHIT_RUN.",9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,0,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,3,American Samoa,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,6,California,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,14,Guam,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,36,New York,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,91,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,92,No Registration,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,93,Multiple State Registration,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,94,U.S. Government Tags (includes military),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,95,Canada,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,96,Mexico,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,97,Other Foreign Country*,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,98,Other Registration (includes Native American Indian Nations),1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,OWNER,owner,Registered Vehicle Owner,This data element identifies the type of registered owner of the vehicle.,This data element also appears in the Parkwork data file as POWNER.,0,"Not Applicable, Vehicle Not Registered",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,OWNER,owner,Registered Vehicle Owner,This data element identifies the type of registered owner of the vehicle.,This data element also appears in the Parkwork data file as POWNER.,1,Driver (in this crash) was  Registered Owner,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,OWNER,owner,Registered Vehicle Owner,This data element identifies the type of registered owner of the vehicle.,This data element also appears in the Parkwork data file as POWNER.,2,Driver (in this crash) Not Registered Owner (Other Private Owner Listed),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,OWNER,owner,Registered Vehicle Owner,This data element identifies the type of registered owner of the vehicle.,This data element also appears in the Parkwork data file as POWNER.,3,Vehicle Registered as Business/Company/Government Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,OWNER,owner,Registered Vehicle Owner,This data element identifies the type of registered owner of the vehicle.,This data element also appears in the Parkwork data file as POWNER.,4,Vehicle Registered as Rental Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,OWNER,owner,Registered Vehicle Owner,This data element identifies the type of registered owner of the vehicle.,This data element also appears in the Parkwork data file as POWNER.,5,Vehicle was Stolen (reported by police),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,OWNER,owner,Registered Vehicle Owner,This data element identifies the type of registered owner of the vehicle.,This data element also appears in the Parkwork data file as POWNER.,6,Driverless/Motor Vehicle Parked/Stopped Off Roadway,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,OWNER,owner,Registered Vehicle Owner,This data element identifies the type of registered owner of the vehicle.,This data element also appears in the Parkwork data file as POWNER.,9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",1,American Motors,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",2,Jeep / Kaiser-Jeep / Willys- Jeep,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",3,AM General,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",6,Chrysler,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",7,Dodge,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",8,Imperial,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",9,Plymouth,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",10,Eagle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",12,Ford,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",13,Lincoln,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",14,Mercury,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",18,Buick / Opel,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",19,Cadillac,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",20,Chevrolet,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",21,Oldsmobile,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",22,Pontiac,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",23,GMC,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",24,Saturn,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",25,Grumman,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",26,Coda,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",29,Other Domestic Manufacturers,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",30,Volkswagen,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",31,Alfa Romeo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",32,Audi,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",33,Austin/Austin Healey,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",34,BMW,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",35,Datsun/Nissan,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",36,Fiat,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",37,Honda,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",38,Isuzu,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",39,Jaguar,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",40,Lancia,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",41,Mazda,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",42,Mercedes-Benz,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",43,MG,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",44,Peugeot,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",45,Porsche,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",46,Renault,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",47,Saab,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",48,Subaru,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",49,Toyota,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",50,Triumph,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",51,Volvo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",52,Mitsubishi,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",53,Suzuki,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",54,Acura,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",55,Hyundai,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",56,Merkur,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",57,Yugo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",58,Infiniti,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",59,Lexus,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",60,Daihatsu,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",61,Sterling,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",62,Land Rover,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",63,KIA,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",64,Daewoo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",65,Smart,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",67,Scion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",69,Other Import,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",70,BSA,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",71,Ducati,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",72,Harley-Davidson,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",73,Kawasaki,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",74,Moto-Guzzi,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",75,Norton,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",76,Yamaha,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",77,Victory,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",80,Brockway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",81,Diamond Reo/Reo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",82,Freightliner,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",83,FWD,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",84,International Harvester/Navistar,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",85,Kenworth,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",86,Mack,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",87,Peterbilt,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",88,Iveco/Magirus,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",89,White/Autocar White/GMC,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",90,Bluebird,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",91,Eagle Coach,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",92,Gillig,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",93,MCI,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",94,Thomas Built,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",97,Not Reported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",98,Other Make,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",99,Unknown Make,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MODEL,model,Vehicle Model,This data element identifies the NCSA model of this vehicle within a given NCSA make.,"Prior to 2020 this data element’s name was ""Vehicle Model"" and the Data Element ID was V10. This data element also appears in the Person data file and in the Parkwork data file as PMODEL.",NA,(Self-evident),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1001,American Motors Rambler/American,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1002,American Motors Rebel/Matador/Marlin,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1003,American Motors Ambassador,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1004,American Motors Pacer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1005,American Motors AMX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1006,American Motors Javelin,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1007,American Motors Hornet/Concord,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1008,American Motors Spirit/Gremlin,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1009,American Motors Eagle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1010,American Motors Eagle SX-4,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1398,American Motors Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1399,American Motors Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2001,Jeep / Kaiser-Jeep / Willys- Jeep Compass,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2401,Jeep / Kaiser-Jeep / Willys- Jeep CJ-2/CJ-3/CJ-4,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2402,Jeep / Kaiser-Jeep / Willys- Jeep CJ-5/CJ-6/CJ-7/CJ-8,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2403,Jeep / Kaiser-Jeep / Willys- Jeep YJ series/Wrangler,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2404,Jeep / Kaiser-Jeep / Willys- Jeep Cherokee (1984-on) (For Grand Cherokee for 2014 on use 02-422.),1,1,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2405,Jeep / Kaiser-Jeep / Willys- Jeep Liberty,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2406,Jeep / Kaiser-Jeep / Willys- Jeep Commander,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2407,Jeep / Kaiser-Jeep / Willys- Jeep Patriot,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2408,Jeep / Kaiser-Jeep / Willys- Jeep Renegade,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2421,Jeep / Kaiser-Jeep / Willys- Jeep Cherokee (thru 1983),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2422,Jeep / Kaiser-Jeep / Willys- Jeep Grand Cherokee (For 2014 on.  Use model 403 for model years prior to 2013.),1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2431,Jeep / Kaiser-Jeep / Willys- Jeep Grand Wagoneer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2481,Jeep / Kaiser-Jeep / Willys- Jeep Pick-up,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2482,Jeep / Kaiser-Jeep / Willys- Jeep Comanche,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2498,Jeep / Kaiser-Jeep / Willys- Jeep Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2499,Jeep / Kaiser-Jeep / Willys- Jeep Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2999,Jeep / Kaiser-Jeep / Willys- Jeep Unknown (JEEP),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3401,AM General Dispatcher,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3402,AM General Hummer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3421,"AM General Hummer (SUV from 1993-2003; see 431 for 2004 on) (for Pickup, see model 481)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3431,AM General Hummer (2004 on; see model 421 for 1993-2003),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3441,AM General MV-1,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3466,AM General Dispatcher,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3481,AM General Hummer (Pickup) (for SUV see model 421 for 1993-2003; see 431 for 2004 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3482,AM General Hummer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3498,AM General Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3499,AM General Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3884,AM General Medium/Heavy Truck,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3898,AM General Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3983,"AM General Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3988,AM General Other(bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3989,AM General Unknown Bus Type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3998,AM General Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3999,AM General Unknown (AM GENERAL),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6009,Chrysler Cordoba,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6010,Chrysler New Yorker (thru 78)/ Newport/5th Avenue/Imperial (1979-83) (excludes all FWD),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6014,Chrysler New Yorker/E-Class/Imperial/ Fifth Avenue,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6015,Chrysler Laser,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6016,Chrysler LeBaron,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6017,Chrysler LeBaron GTS/GTC,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6018,Chrysler 200,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6021,Chrysler SRT Viper,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6031,Chrysler TC (Maserati Sport),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6035,Chrysler Conquest,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6041,Chrysler Concorde,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6042,Chrysler LHS,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6043,Chrysler Sebring,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6044,Chrysler Cirrus,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6050,Chrysler Executive,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6051,Chrysler 300M/300/300C/300S,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6052,Chrysler PT Cruiser,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6053,"Chrysler Prowler (2002 on)  (1997,1999-01 see Plymouth)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6054,Chrysler Pacifica,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6055,Chrysler Crossfire,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6398,Chrysler Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6399,Chrysler Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6421,Chrysler Aspen,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6441,Chrysler Town and Country,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6442,Chrysler Voyager (2000 on; 1984-00 see Plymouth),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6499,Chrysler Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6999,Chrysler Unknown (CHRYSLER),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7001,Dodge Dart,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7002,Dodge Coronet/Magnum/ Charger (thru 1978),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7003,Dodge Polara/Monaco/ Royal Monaco,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7004,Dodge Viper,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7005,Dodge Challenger,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7006,Dodge Aspen,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7007,Dodge Diplomat,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7008,Dodge Omni/Charger (1983 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7009,Dodge Mirada,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7010,Dodge St Regis,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7011,Dodge Aries (K),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7012,Dodge 400,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7013,Dodge Rampage (car-based pickup),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7014,Dodge 600,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7015,Dodge Daytona,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7016,Dodge Lancer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7017,Dodge Shadow,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7018,Dodge Dynasty,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7019,Dodge Spirit,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7020,Dodge Neon,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7021,Dodge Magnum,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7024,Dodge Charger,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7025,Dodge Caliber,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7026,Dodge Avenger,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7027,Dodge Journey,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7028,Dodge Challenger (2008 on; for 1970-74 see model 005),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7029,Dodge Dart (2013 on. See model 001 for 1960-1976.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7030,Dodge Barracuda,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7033,Dodge Challenger,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7034,Dodge Colt  (includes 2WD Vista),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7035,Dodge Conquest,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7039,Dodge Stealth,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7040,Dodge Monaco,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7041,Dodge Intrepid,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7042,Dodge Avenger,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7043,Dodge Stratus,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7398,Dodge Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7399,Dodge Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7401,Dodge RaiderSport,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7402,Dodge Durango (1998-2003 only; see model 422 for 2004 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7403,Dodge Nitro,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7421,Dodge Ramcharger,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7422,Dodge Durango (2004 on; see 402 for 1998-2003 models),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7441,Dodge Vista Van,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7442,Dodge Caravan/Grand Caravan,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7443,Dodge Ram C/V,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7444,Dodge Promaster City,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7461,Dodge B-Series Van/Ram Van/ Ram Wagon,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7462,Dodge Sprinter,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7463,Dodge Ram Promaster,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7470,Dodge Van Derivative,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7471,"Dodge D50, Colt pickup, Ram 50/Ram 100",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7472,Dodge Dakota,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7481,"Dodge D, W-Series pickup",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7482,Dodge Ram Pickup,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7498,Dodge Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7499,Dodge Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7850,Dodge Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7870,Dodge Medium/Heavy Van-Based Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7880,"Dodge Medium/Heavy Pickup (pickup-style only - over 10,000 lbs)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7881,Dodge Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7882,Dodge Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7883,Dodge Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7884,Dodge Medium/Heavy -Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7890,Dodge Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7898,Dodge Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7981,Dodge Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7988,Dodge Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7989,Dodge Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7998,Dodge Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7999,Dodge Unknown (DODGE),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",8010,Imperial Imperial,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",8398,Imperial Other (automobile,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",8399,Imperial Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9001,Plymouth Valiant/Scamp/Duster (thru 1976),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9002,Plymouth Satellite/Belvedere,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9003,Plymouth Fury (Fury Gran thru `78),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9004,Plymouth Gran Fury (`80 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9005,Plymouth Barracuda,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9006,Plymouth Volare`,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9007,Plymouth Caravelle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9008,Plymouth Horizon/Turismo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9011,Plymouth Reliant (K),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9013,Plymouth Scamp-(car-based p/u),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9017,Plymouth Sundance,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9019,Plymouth Acclaim,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9020,"Plymouth Neon (2002 and on, see Dodge)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9031,Plymouth Cricket,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9032,Plymouth Arrow,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9033,Plymouth Sapporo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9034,Plymouth Champ/Colt import (includes 2WD Vista),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9035,Plymouth Conquest,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9037,Plymouth Laser,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9038,Plymouth Breeze,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9039,"Plymouth Prowler (2002 and on, see Chrysler)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9398,Plymouth Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9399,Plymouth Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9421,Plymouth Trailduster,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9441,Plymouth Vista Van,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9442,"Plymouth Voyager (minivan) (2001 and on, see Chrysler)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9461,Plymouth Van-fullsize (B-series),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9471,Plymouth Arrow pickup (foreign),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9498,Plymouth Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9499,Plymouth Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9998,Plymouth Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9999,Plymouth Unknown (PLYMOUTH),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10034,Eagle Summit (excludes wagon),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10037,Eagle Talon,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10040,Eagle Premier,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10041,Eagle Vision,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10044,Eagle Medallion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10045,Eagle Summit Wagon,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10398,Eagle Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10399,Eagle Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12001,Ford Falcon,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12002,Ford Fairlane,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12003,Ford Mustang/Mustang II,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12004,Ford Thunderbird (all sizes),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12005,Ford LTD II,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12006,Ford LTD/Custom/Galaxy (all sizes),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12007,Ford Ranchero,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12008,Ford Maverick,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12009,Ford Pinto,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12010,Ford Torino/Gran Torino/Elite,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12011,Ford Granada,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12012,Ford Fairmont,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12013,Ford Escort/EXP/ZX2,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12015,Ford Tempo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12016,Ford Crown Victoria,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12017,Ford Taurus/Taurus X,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12018,Ford Probe,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12021,Ford Five Hundred,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12022,Ford Freestyle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12023,Ford Fusion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12024,Ford Edge,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12025,Ford Flex,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12026,Ford City,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12027,Ford C-Max,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12031,Ford English Ford,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12032,Ford Fiesta,1,1,1,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12033,Ford Festiva,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12034,Ford Laser,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12035,Ford Contour,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12036,Ford Aspire,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12037,Ford Focus,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12038,Ford GT,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12398,Ford Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12399,Ford Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12401,Ford Bronco (thru 1977)/Bronco II/Explorer/Explorer Sport,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12402,Ford Escape,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12421,Ford Bronco-fullsize (1978-on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12422,Ford Expedition,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12423,Ford Excursion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12441,Ford Aerostar,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12442,Ford Windstar,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12443,Ford Freestar,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12444,Ford Transit Connect,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12461,Ford E-Series Van/Econoline,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12462,Ford Transit,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12470,Ford Van Derivative,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12471,Ford Ranger,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12472,Ford Courier,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12473,Ford Explorer Sport Trac,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12481,Ford F-Series pickup,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12498,Ford Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12499,Ford Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12850,Ford Motorhome,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12870,Ford Medium/Heavy Van-Based Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12880,"Ford Medium/Heavy Pickup (pickup-style only - over 10,000 lbs)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12881,Ford Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12882,Ford Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12883,Ford Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12884,Ford Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12890,Ford Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12898,Ford Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12981,Ford Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12988,Ford Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12989,Ford Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12998,Ford Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12999,Ford Unknown (FORD),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13001,Lincoln Continental (thru `81)/ Town Car,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13002,Lincoln Mark,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13005,Lincoln Continental (`82 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13011,Lincoln Versailles,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13012,Lincoln LS,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13013,Lincoln Zephyr/MKZ,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13014,Lincoln MKX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13015,Lincoln MKS,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13016,Lincoln MKT,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13398,Lincoln Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13399,Lincoln Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13401,Lincoln Aviator,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13402,Lincoln MKC,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13421,Lincoln Navigator,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13481,Lincoln Blackwood,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13482,Lincoln Mark LT,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13498,Lincoln Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13499,Lincoln Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13999,Lincoln Unknown (LINCOLN),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14002,Mercury Cyclone,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14003,Mercury Capri- domestic (1967 see 008),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14004,Mercury Cougar/XR7 (1967-1997),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14006,Mercury Marquis/Monterey (car version; for van version 2004 on see code 444) /Grand Marquis,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14008,Mercury Comet,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14009,Mercury Bobcat,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14010,Mercury Montego (prior to 1976; for 2005 on see code 020),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14011,Mercury Monarch,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14012,Mercury Zephyr,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14013,Mercury Lynx/LN7,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14015,Mercury Topaz,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14017,Mercury Sable,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14020,Mercury Montego (2005 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14021,Mercury Milan,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14031,Mercury Capri-foreign,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14033,Mercury Pantera-foreign,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14036,Mercury Tracer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14037,Mercury Mystique,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14038,Mercury Cougar (1999 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14039,Mercury Marauder,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14398,Mercury Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14399,Mercury Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14401,Mercury Mountaineer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14402,Mercury Mariner,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14443,Mercury Villager,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14444,Mercury Monterey (van version; for car version prior to 2004 see code 006),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14498,Mercury Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14499,Mercury Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14999,Mercury Unknown (MERCURY),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18001,Buick / Opel Special/Skylark,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18002,"Buick / Opel LeSabre/Centurion/ Estate Wagon, Invicta, Custom, Limited, T-Type, Ltd, C.M.I, LE",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18003,"Buick / Opel Electra/Electra 225/ Park Limited, Park Avenue, Ultra, Base",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18004,Buick / Opel Roadmaster,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18005,Buick / Opel Riviera,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18007,Buick / Opel Century,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18008,Buick / Opel Apollo/Skylark,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18010,Buick / Opel Regal (RWD only),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18012,Buick / Opel Skyhawk,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18015,Buick / Opel Skylark (76-85),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18018,Buick / Opel Somerset/Skylark,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18019,Buick / Opel Regal (2011 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18020,Buick / Opel Regal (FWD),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18021,Buick / Opel Reatta,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18022,Buick / Opel LaCrosse,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18023,Buick / Opel Lucerne,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18024,Buick / Opel Enclave (2008-12 model years only.  For 2013 on see model 421.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18025,Buick / Opel Verano,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18031,Buick / Opel Opel Kadett,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18032,Buick / Opel Opel Manta,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18033,Buick / Opel Opel GT,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18034,Buick / Opel Opel Isuzu,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18398,Buick / Opel Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18399,Buick / Opel Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18401,Buick / Opel Rendezvous,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18402,Buick / Opel Rainier,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18404,Buick / Opel Encore,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18421,Buick / Opel Enclave (2013 on.  See model 024 for 2008-12 model years.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18441,Buick / Opel Terraza,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18498,Buick / Opel Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18499,Buick / Opel Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18999,Buick / Opel Unknown BUICK,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19003,"Cadillac Deville/Fleetwood,Coupe de Ville, Sedan de Ville, Fleetwood Brougham, Fleetwood 60 Special, d`Elegan",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19004,Cadillac Limousine,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19005,Cadillac Eldorado,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19006,Cadillac Commercial Series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19009,Cadillac Allante`,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19014,Cadillac Seville,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19016,Cadillac Cimarron,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19017,Cadillac Catera,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19018,Cadillac CTS/CTC,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19019,Cadillac XLR,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19020,Cadillac SRX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19021,Cadillac STS,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19022,Cadillac DTS,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19023,Cadillac XTS,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19024,Cadillac ATS,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19025,Cadillac ELR,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19398,Cadillac Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19399,Cadillac Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19421,Cadillac Escalade/ESV (from 2004 on; see 431 for 2003 only),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19431,Cadillac Escalade ESV,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19480,Cadillac Escalade EXT (from 2002 -2006; for 2007 on see 481),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19481,Cadillac Escalade EXT (from 2007 on; see 480 for 2002-2006),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19498,Cadillac Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19499,Cadillac Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19999,Cadillac Unknown CADILLAC,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20001,"Chevrolet Chevelle/Malibu Classic, Councours, Laguna**, S-3, Greenbriar, Estate, 300,SS-396/454, Deluxe",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20002,"Chevrolet Impala/Caprice (For SS from 2014 on, use 20-021.)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20004,Chevrolet Corvette,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20006,Chevrolet Corvair,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20007,Chevrolet El Camino,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20008,Chevrolet Nova (-`79),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20009,Chevrolet Camaro,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20010,Chevrolet Monte Carlo (thru `88),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20011,Chevrolet Vega,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20012,Chevrolet Monza,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20013,Chevrolet Chevette,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20015,Chevrolet Citation,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20016,Chevrolet Cavalier,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20017,Chevrolet Celebrity,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20019,Chevrolet Beretta/Corsica,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20020,Chevrolet Lumina,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20021,Chevrolet SS (For 2014 on.  For Impala/Caprice SS use model 20-002.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20022,Chevrolet Cobalt,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20023,Chevrolet HHR,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20024,Chevrolet Traverse (2009-2012 only.  For 2013 on see model 423.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20025,Chevrolet Cruze,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20026,Chevrolet Volt,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20027,Chevrolet Caprice PPV,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20028,Chevrolet Sonic,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20029,Chevrolet Spark,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20031,Chevrolet Spectrum,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20032,Chevrolet Nova/Geo Prizm/Prism,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20033,Chevrolet Sprint/Geo Sprint,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20034,Chevrolet Geo Metro/Metro,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20035,Chevrolet Geo Storm,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20036,Chevrolet Monte Carlo (1995 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20037,Chevrolet Malibu/Malibu Maxx,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20038,Chevrolet SSR,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20039,Chevrolet Aveo/Aveo 5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20398,Chevrolet Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20399,Chevrolet Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20401,"Chevrolet S-10 Blazer/TrailBlazer (2002 only; for 2003 on, see 403)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20402,Chevrolet Geo Tracker/Tracker,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20403,"Chevrolet TrailBlazer (2003 on; for 2002 model, see 401)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20404,Chevrolet Equinox,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20405,Chevrolet Captiva,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20406,Chevrolet Trax,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20421,Chevrolet Fullsize Blazer/Tahoe,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20422,Chevrolet Suburban (from 2004 on; see 431 for 1950-2003),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20423,Chevrolet Traverse (2013 on.  For 2009-2012 see model 024.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20431,Chevrolet Suburban (from 1950-2003;see 422 for 2004 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20441,Chevrolet Astro Van,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20442,Chevrolet Lumina APV,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20443,Chevrolet Venture,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20444,Chevrolet Uplander,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20461,Chevrolet G-series van,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20466,Chevrolet P-series van,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20470,Chevrolet Van derivative,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20471,Chevrolet S-10/T-10 Pickup,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20472,Chevrolet LUV,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20473,Chevrolet Colorado,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20481,"Chevrolet C, K, R, V-series pickup/Silverado",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20482,Chevrolet Avalanche,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20498,Chevrolet Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20499,Chevrolet Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20850,Chevrolet Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20870,Chevrolet Medium/Heavy Van-Based Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20880,"Chevrolet Medium/Heavy Pickup (pickup-style only - over 10,000 lbs)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20881,Chevrolet Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20882,Chevrolet Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20883,Chevrolet Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20884,Chevrolet Medium/Heavy -Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20890,Chevrolet Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20898,Chevrolet Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20981,Chevrolet Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20988,Chevrolet Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20989,Chevrolet Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20998,Chevrolet Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20999,Chevrolet Unknown (CHEVROLET),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21001,Oldsmobile Cutlass (RWD-only),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21002,Oldsmobile Delta 88/LSS,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21003,Oldsmobile Ninety-Eight/Regency,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21005,Oldsmobile Toronado,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21006,Oldsmobile Commercial Series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21012,Oldsmobile Starfire,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21015,Oldsmobile Omega,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21016,Oldsmobile Firenza,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21017,Oldsmobile Ciera,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21018,Oldsmobile Calais,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21020,Oldsmobile Cutlass (FWD),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21021,Oldsmobile Achieva/Alero,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21022,Oldsmobile Aurora,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21023,Oldsmobile Intrigue,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21398,Oldsmobile Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21399,Oldsmobile Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21401,Oldsmobile Bravada,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21441,Oldsmobile Silhouette,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21499,Oldsmobile Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21999,Oldsmobile Unknown (OLDSMOBILE),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22001,Pontiac Lemans/ Tempest (thru 1970),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22002,Pontiac Bonneville/Catalina/ Parisienne,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22005,Pontiac Fiero,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22008,Pontiac Ventura/GTO,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22009,Pontiac Firebird/Trans AM,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22010,Pontiac Grand Prix (RWD),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22011,Pontiac Astre,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22012,Pontiac Sunbird (thru 1980;1985 on see model 016),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22013,Pontiac T-1000/1000,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22015,Pontiac Phoenix,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22016,Pontiac Sunbird (1985-1994)/J-2000/Sunfire (1995 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22017,Pontiac 6000,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22018,Pontiac Grand AM,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22019,Pontiac G5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22020,Pontiac Grand Prix (FWD),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22022,Pontiac G6,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22023,Pontiac Solstice,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22024,Pontiac G8,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22025,Pontiac G3,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22026,Pontiac G8-ST,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22031,Pontiac Lemans (1988-on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22032,Pontiac Vibe,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22398,Pontiac Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22399,Pontiac Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22401,Pontiac Aztek,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22403,Pontiac Torrent,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22441,Pontiac Trans Sport/ Montana/SV6,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22499,Pontiac Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22999,Pontiac Unknown (PONTIAC),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23007,GMC Caballero,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23008,GMC Acadia (2007-2012 only.  For 2013 on see model 423.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23399,GMC Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23401,GMC Jimmy/Typhoon/Envoy,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23402,GMC Terrain,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23421,GMC Fullsize Jimmy/Yukon,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23422,GMC Suburban/Yukon XL (2004 on; see 431 for 1950- 2003),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23423,GMC Acadia (2013 on. For 2007-2012 see model 008.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23431,GMC Suburban/Yukon XL (2000 on) (1950-2003 only; see 422 for 2004 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23441,GMC Safari (Minivan),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23461,GMC G-series van/Savana,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23466,GMC P-series van,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23470,GMC Van derivative,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23471,GMC S15/T15/Sonoma,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23472,GMC Canyon,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23481,"GMC C, K, R, V-series pickup/     Sierra",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23498,GMC Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23499,GMC Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23850,GMC Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23870,GMC Medium/Heavy Van-Based Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23880,"GMC Medium/Heavy Pickup (pickup-style only - over 10,000 lbs",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23881,GMC Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23882,GMC Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23883,GMC Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23884,GMC Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23890,GMC Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23898,GMC Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23981,GMC Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23988,GMC Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23989,GMC Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23998,GMC Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23999,GMC Unknown (GMC),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24001,Saturn SL,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24002,Saturn SC,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24003,Saturn SW,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24004,Saturn EV1/EGV1*,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24005,Saturn LS,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24006,Saturn LW,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24007,Saturn Ion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24008,Saturn Sky,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24009,Saturn Aura,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24010,Saturn Outlook,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24011,Saturn Astra,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24398,Saturn Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24399,Saturn Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24401,Saturn Vue,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24441,Saturn Relay,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24499,Saturn Unknown (Light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24999,Saturn Unknown (SATURN),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25401,Grumman LLV,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25441,Grumman Step-in van,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25498,Grumman Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25499,Grumman Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25881,Grumman Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25882,Grumman Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25883,Grumman Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25884,Grumman Medium/Heavy - engine location unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25890,Grumman Medium/Heavy - entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25898,Grumman Other (Medium/Heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25983,"Grumman Bus: Flat front, rear engine",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25988,Grumman Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25989,Grumman Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25999,Grumman Unknown (GRUMMAN/ GRUMMAN-OLSON),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",26001,Coda Coda,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",26398,Coda Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",26399,Coda Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29001,Other Domestic Manufacturers Studabaker/Avanti,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29002,Other Domestic Manufacturers Checker,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29003,Other Domestic Manufacturers Panoz,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29004,Other Domestic Manufacturers Saleen,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29005,Other Domestic Manufacturers Tesla,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29398,Other Domestic Manufacturers Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29399,Other Domestic Manufacturers Unknown Make,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30031,Volkswagen Karmann Ghia,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30032,Volkswagen Beetle 1300/1500,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30033,Volkswagen Super Beetle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30034,Volkswagen 411/412,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30035,Volkswagen Squareback/Fastback,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30036,Volkswagen Rabbit,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30037,Volkswagen Dasher,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30038,Volkswagen Scirocco,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30040,Volkswagen Jetta/Jetta SportsWagen,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30041,Volkswagen Quantum,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30042,Volkswagen Golf/Cabriolet/Cabrio/GTI,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30043,Volkswagen Rabbit Pickup,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30044,Volkswagen Fox,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30045,Volkswagen Corrado,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30046,Volkswagen Passat (CC - 2008 thru 2011; see 052 for 2012 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30047,Volkswagen New Beetle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30048,Volkswagen Phaeton,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30051,Volkswagen Eos,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30052,Volkswagen CC (For 2012 on. See model 046 for 2008-2011.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30398,Volkswagen Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30399,Volkswagen Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30401,Volkswagen The Thing (181),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30402,Volkswagen Tiguan,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30421,Volkswagen Touareg/Tourareg 2,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30441,Volkswagen Vanagon/Camper,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30442,Volkswagen Eurovan,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30443,Volkswagen Routan,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30498,Volkswagen Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30499,Volkswagen Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30998,Volkswagen Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30999,Volkswagen Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31031,Alfa Romeo Spider (Spyder),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31032,Alfa Romeo Sports Sedan,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31033,Alfa Romeo Sprint/Special,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31034,Alfa Romeo GTV-6,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31035,Alfa Romeo 164 (Alpha 164),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31036,Alfa Romeo 4c,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31037,Alfa Romeo Giulia,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31398,Alfa Romeo Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31399,Alfa Romeo Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32031,Audi Super 90,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32032,Audi 100,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32033,Audi Fox,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32034,Audi 4000,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32035,Audi 5000,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32036,Audi 80/90,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32037,Audi 200,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32038,Audi V-8 Quattro,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32039,Audi Coupe Quattro,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32040,Audi S4 (1992-1994; 2000-2011 only. See model 055 for 2012 on)/S6 (1992-1994; 2000-2011 only.  See model 056 for 2013 on.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32041,Audi Cabriolet (1994-1998),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32042,Audi A6,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32043,Audi A4,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32044,Audi A8,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32045,Audi TT/TTS,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32046,Audi S8,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32047,Audi Allroad (2001-05 only.  See 403 for 2013 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32048,Audi A3,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32049,Audi A5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32050,Audi R8,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32051,Audi A7,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32052,Audi S5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32054,Audi RS5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32055,Audi S4 (2012 on only.  See model 040 for 1992-1994; 2000-2011),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32056,Audi S6 (2013 on.  See model 040 for 1992-1994; 2000-2011),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32057,Audi S7,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32058,Audi RS7,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32059,Audi S3,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32398,Audi Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32399,Audi Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32401,Audi Q7,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32402,Audi Q5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32403,Audi Allroad(2013 on),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32404,Audi SQ5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32405,Audi Q3,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32499,Audi Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32999,Audi Unknown (AUDI),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33031,Austin/Austin Healey Marina,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33032,Austin/Austin Healey America,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33033,Austin/Austin Healey Healey Sprite,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33034,Austin/Austin Healey Healey 100/3000,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33035,Austin/Austin Healey Mini/Mini Cooper/Mini Moke,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33398,Austin/Austin Healey Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33399,Austin/Austin Healey Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34031,"BMW 1600, 1800, 2000,2002",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34032,BMW Coupe (before 1975),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34033,BMW Bavarian Sedan,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34034,BMW 3-series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34035,BMW 5-series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34036,BMW 6-series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34037,BMW 7-series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34038,BMW 8-series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34039,BMW Z3,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34040,BMW Z8,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34041,BMW V5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34042,BMW Z4,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34043,BMW 1-Series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34044,BMW X6,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34045,BMW i3,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34046,BMW i8,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34047,BMW 4-Series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34048,BMW 2-Series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34049,BMW X4,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34398,BMW Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34399,BMW Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34401,BMW X5,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34402,BMW X3,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34403,BMW X1,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34499,BMW Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34703,BMW 125-349cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34705,BMW 450-749cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34706,BMW 750cc and over,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34709,BMW Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34999,BMW Unknown (BMW),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35031,Datsun/Nissan F-10,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35032,Datsun/Nissan 200SX/240SX,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35033,Datsun/Nissan 210/1200/B210,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35034,"Datsun/Nissan Z-car, ZX",1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35035,Datsun/Nissan 310,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35036,Datsun/Nissan 510,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35037,Datsun/Nissan 610,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35038,Datsun/Nissan 710,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35039,Datsun/Nissan 810/Maxima,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35040,Datsun/Nissan Roadster,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35041,Datsun/Nissan 311/411,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35042,Datsun/Nissan Stanza,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35043,Datsun/Nissan Sentra,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35044,Datsun/Nissan Pulsar,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35045,Datsun/Nissan Micra,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35046,Datsun/Nissan NX 1600/2000,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35047,Datsun/Nissan Altima,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35048,Datsun/Nissan 350Z/370Z,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35049,Datsun/Nissan Murano,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35050,Datsun/Nissan Versa,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35051,Datsun/Nissan Rogue,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35052,Datsun/Nissan Cube,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35053,Datsun/Nissan GT-R,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35055,Datsun/Nissan Leaf,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35398,Datsun/Nissan Other (automobile),1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35399,Datsun/Nissan Unknown (automobile),1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35401,Datsun/Nissan Pathfinder,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35402,Datsun/Nissan Xterra,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35403,Datsun/Nissan Juke,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35421,Datsun/Nissan Pathfinder Armada,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35441,Datsun/Nissan Van,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35442,Datsun/Nissan Axxess,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35443,Datsun/Nissan Quest,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35444,Datsun/Nissan Altra EV*,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35446,Datsun/Nissan NV200/eNV200,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35461,Datsun/Nissan NV,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35471,Datsun/Nissan Datsun/Nissan Pickup 1955-1997),1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35472,Datsun/Nissan Frontier (1998 on),1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35473,Datsun/Nissan Titan (from 2004-06; see 481 for 2007 on),1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35481,Datsun/Nissan Titan (from 2007 on; see 473 for 2004-06),1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35498,Datsun/Nissan Other (light truck),1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35499,Datsun/Nissan Unknown (light truck),1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35870,Datsun/Nissan Medium Heavy Van-Based Vehicle,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35883,Datsun/Nissan Medium/Heavy - COE high entry,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35898,Datsun/Nissan Other (medium/heavy truck),1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35999,Datsun/Nissan Unknown (NISSAN/DATSUN),1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36031,Fiat 124 (Coupe/Sedan),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36032,Fiat 124 Spider/Racer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36033,Fiat Brava/131,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36034,Fiat 850 (Coupe/Spider),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36035,Fiat 128,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36036,Fiat X-1/9,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36037,Fiat Strada,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36038,Fiat 500/500c,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36398,Fiat Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36399,Fiat Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36401,Fiat 500L,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36499,Fiat Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36882,Fiat Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36883,Fiat Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36890,Fiat Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36898,Fiat Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36998,Fiat Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36999,Fiat Unknown (FIAT),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37031,"Honda Civic/CRX, del Sol",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37032,Honda Accord,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37033,Honda Prelude,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37034,Honda 600,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37035,Honda S2000,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37036,Honda EV Plus*,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37037,Honda Insight,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37038,Honda FCX,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37039,Honda Fit,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37041,Honda CR-Z,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37398,Honda Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37399,Honda Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37401,Honda Passport,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37402,Honda CR-V,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37403,Honda Element,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37421,Honda Pilot,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37441,Honda Odyssey,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37471,Honda Ridgeline,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37498,Honda Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37499,Honda Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37701,Honda 0- 50 cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37702,Honda 51-124 cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37703,Honda 125-349 cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37704,Honda 350-449 cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37705,Honda 450-749 cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37706,Honda 750 cc or greater,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37709,Honda Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37732,Honda 51-124cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37733,Honda 125-349cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37734,Honda 350cc or greater (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37739,Honda Unknown cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37998,Honda (Other Vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37999,Honda Unknown (HONDA),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38031,Isuzu I-Mark,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38032,Isuzu Impulse,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38033,Isuzu Stylus,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38398,Isuzu Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38399,Isuzu Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38401,Isuzu Trooper/Trooper II,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38402,Isuzu Rodeo/ Rodeo Sport,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38403,Isuzu Amigo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38404,Isuzu VehiCROSS,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38405,Isuzu Axiom,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38421,Isuzu Ascender,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38441,Isuzu Oasis,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38471,Isuzu P`up (pickup),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38472,Isuzu Hombre,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38473,Isuzu i-280,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38474,Isuzu i-350,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38498,Isuzu Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38499,Isuzu Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38881,Isuzu Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38882,"Isuzu Medium/Heavy - COE, low entry",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38883,"Isuzu Medium/Heavy - COE, high entry",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38884,Isuzu Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38890,Isuzu Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38898,Isuzu Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38981,Isuzu Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38982,"Isuzu Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38983,Isuzu Bus: Rear engine Flat front,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38988,Isuzu Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38989,Isuzu Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38999,Isuzu Unknown (ISUZU),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39031,"Jaguar XJ-S, XK8 Coupe",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39032,Jaguar XJ/XJ6/12/XJR/XJ8/  XJ8L Sedan/Coupe,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39033,Jaguar XK-E,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39034,Jaguar S-Type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39035,Jaguar XKR/XK,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39036,Jaguar X-Type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39037,Jaguar XF/XFR,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39038,Jaguar F-Type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39398,Jaguar Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39399,Jaguar Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",40031,Lancia Beta Sedan - HPE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",40032,Lancia Zagato,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",40033,Lancia Scorpion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",40398,Lancia Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",40399,Lancia Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41031,Mazda RX2,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41032,Mazda RX3,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41033,Mazda RX4,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41034,Mazda RX7,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41035,NA,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41036,Mazda Cosmo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41037,Mazda 626,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41038,Mazda 808,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41039,Mazda Mizer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41040,Mazda R-100,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41041,Mazda 616/618,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41042,Mazda 1800,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41043,Mazda 929,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41044,Mazda MX-6,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41045,Mazda Miata/MX-5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41046,Mazda MX-3,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41047,Mazda Millenia,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41048,Mazda MP3,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41049,Mazda RX-8,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41050,Mazda Mazda6,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41051,Mazda Mazda3,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41052,Mazda Mazda5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41053,Mazda CX-7,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41054,Mazda CX-9 (2007-12 only.For 2013 on see model 421.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41055,Mazda Mazda2,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41398,Mazda Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41399,Mazda Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41401,Mazda Navajo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41402,Mazda Tribute,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41403,Mazda CX5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41421,Mazda CX-9 (2013 on. See model 054 for 2007-12 model years.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41441,Mazda MPV,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41471,Mazda Pickup/ B-Series Pickup,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41498,Mazda Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41499,Mazda Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41999,Mazda Unknown (MAZDA),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42031,Mercedes-Benz 200/220/230/240/ 250/260/280/300/ 320/420,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42032,Mercedes-Benz 230/280 SL,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42033,Mercedes-Benz 300/350/380/450/500/ 560 SL,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42034,Mercedes-Benz 350/380/420/450/560 SLC,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42035,Mercedes-Benz 280/300 SEL,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42036,"Mercedes-Benz 300/380/420/450/500/560/SEL & 500/560, 600 SEC & 300/350 SDL",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42037,Mercedes-Benz 300/380/450 SE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42038,"Mercedes-Benz 600, 6.9 Sedan",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42039,Mercedes-Benz 190,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42040,Mercedes-Benz 300,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42041,Mercedes-Benz 400/500E,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42042,Mercedes-Benz C Class (94 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42043,Mercedes-Benz S Class (95 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42044,Mercedes-Benz SL Class (95 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42045,Mercedes-Benz SLK,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42046,Mercedes-Benz CL Class,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42047,Mercedes-Benz CLK,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42048,Mercedes-Benz E Class (97 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42049,Mercedes-Benz SLR,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42050,Mercedes-Benz R Class,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42051,Mercedes-Benz CLS Class,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42052,Mercedes-Benz SLS Class,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42053,Mercedes-Benz B Class,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42054,Mercedes-Benz CLA Class,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42055,Mercedes-Benz GLA Class,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42398,Mercedes-Benz Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42399,Mercedes-Benz Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42401,Mercedes-Benz M/ML Class,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42402,Mercedes-Benz G Class,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42403,Mercedes-Benz GLK Class,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42421,Mercedes-Benz GL Class,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42461,Mercedes-Benz SPRINTER,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42470,Mercedes-Benz Van derivative,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42498,Mercedes-Benz Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42499,Mercedes-Benz Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42870,Mercedes-Benz Medium Heavy Van-Based Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42881,Mercedes-Benz Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42882,Mercedes-Benz Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42883,Mercedes-Benz Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42884,Mercedes-Benz Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42890,Mercedes-Benz Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42898,Mercedes-Benz Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42981,Mercedes-Benz Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42988,Mercedes-Benz Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42989,Mercedes-Benz Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42998,Mercedes-Benz Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42999,Mercedes-Benz Unknown (MERCEDES-BENZ),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43031,MG Midget,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43032,MG MGB,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43033,MG MGB,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43034,MG MGA,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43035,MG TA/TC/TD/TF,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43036,MG MGC,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43037,MG Magnette/Sports Sedans,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43398,MG Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43399,MG Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44031,Peugeot 304,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44032,Peugeot 403,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44033,Peugeot 404,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44034,Peugeot 504/505,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44035,Peugeot 604,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44036,Peugeot 405,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44398,Peugeot Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44399,Peugeot Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44701,Peugeot 0 - 50 cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44702,Peugeot 51-124cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44709,Peugeot Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44999,Peugeot Unknown (PEUGEOT),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45031,Porsche 911/996,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45032,Porsche 912,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45033,Porsche 914,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45034,Porsche 924,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45035,Porsche 928,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45036,Porsche 930,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45037,Porsche 944,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45038,Porsche 959,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45039,Porsche 968,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45040,Porsche 986/Boxster,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45041,Porsche Cayman,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45042,Porsche Panamera,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45043,Porsche 918,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45398,Porsche Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45399,Porsche Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45401,Porsche Macan,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45421,Porsche Cayenne,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45499,Porsche Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45999,Porsche Unknown(PORSCHE),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46031,Renault LeCar,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46032,Renault Dauphine/10/R-8 Caravelle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46033,Renault 12,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46034,Renault 15,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46035,Renault 16,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46036,Renault 17,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46037,Renault 18i/Sportwagon,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46038,Renault Fuego,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46039,"Renault Alliance/Encore GTA, Convertible",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46041,Renault Alpine,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46044,Renault Medallion **,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46045,Renault Premier**,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46398,Renault Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46399,Renault Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47031,Saab 99/99E/900,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47032,Saab Sonnett,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47033,Saab 95/96,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47034,Saab 9000,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47035,Saab 9-3/9-3X,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47036,Saab 9-5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47037,Saab 9-2X,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47038,Saab 9-4X,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47398,Saab Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47399,Saab Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47401,Saab 9-7x,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47999,Saab Unknown(SAAB),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48031,Subaru Loyale (1990 on)/DL/ FE/G/GF/GL/GLF/STD,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48032,Subaru Star,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48033,Subaru 360,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48034,Subaru Legacy/Outback(prior to 2003 only; see 045 for 2003 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48035,Subaru XT/XT6,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48036,Subaru Justy,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48037,Subaru SVX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48038,Subaru Impreza,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48039,Subaru RX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48043,Subaru Brat,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48044,Subaru Baja,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48045,Subaru Outback (2003 on)(see 034 for prior to 2003),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48046,Subaru BRZ,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48047,Subaru WRX (2015 on; see 038 for prior to 2015.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48398,Subaru Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48399,Subaru Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48401,Subaru Forester,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48402,Subaru B9 Tribeca,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48403,Subaru XV Crosstrek,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48499,Subaru Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48999,Subaru Unknown (SUBARU),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49031,Toyota Corona,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49032,Toyota Corolla,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49033,Toyota Celica,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49034,Toyota Supra,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49035,Toyota Cressida,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49036,Toyota Crown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49037,Toyota Carina,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49038,Toyota Tercel,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49039,Toyota Starlet,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49040,Toyota Camry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49041,Toyota MR-2/MR Spyder,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49042,Toyota Paseo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49043,Toyota Avalon,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49044,Toyota Solara,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49045,Toyota ECHO,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49046,Toyota Prius *,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49047,Toyota Matrix,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49048,Toyota Scion xA,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49049,Toyota Scion xB (2004-2011 only.  See Scion for 2012 on.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49050,Toyota Scion tC (2005-2011 only.  See Scion for 2012 on.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49051,Toyota Yaris,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49052,Toyota Scion xD (2007-2011 only.  See Scion for 2012 on.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49053,Toyota Venza,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49054,Toyota Scion iQ (2010-2011 only.  See Scion for 2012 on.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49398,Toyota Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49399,Toyota Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49401,Toyota 4-Runner,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49402,Toyota RAV4 *,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49403,Toyota Highlander,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49404,Toyota FJ Cruiser,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49421,Toyota Land Cruiser,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49422,Toyota Sequoia,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49441,Toyota Minivan (1984-90)/ Previa (1991 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49442,Toyota Sienna,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49471,Toyota Pickup,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49472,Toyota Tacoma,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49481,Toyota T-100,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49482,Toyota Tundra,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49498,Toyota Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49499,Toyota Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49999,Toyota Unknown (TOYOTA),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50031,Triumph Spitfire,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50032,Triumph GT-6,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50033,Triumph TR4,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50034,Triumph TR6,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50035,Triumph TR7/TR8,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50036,Triumph Herald,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50037,Triumph Stag,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50398,Triumph Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50399,Triumph Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50701,Triumph 0-50cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50702,Triumph 51-124cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50703,Triumph 125-349cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50704,Triumph 350-449cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50705,Triumph 450-749cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50706,Triumph 750cc or greater,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50709,Triumph Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50799,Triumph Unknown (motored cycle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50999,Triumph Unknown (TRIUMPH),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51031,Volvo 122,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51032,Volvo 140/142/144/145 *,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51033,Volvo 164,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51034,Volvo 240 series*/DL/GL/GLT,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51035,Volvo 260 series/GLE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51036,Volvo 1800,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51037,Volvo PV544,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51038,Volvo 760/780,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51039,Volvo 740,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51040,Volvo 940,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51041,Volvo 960,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51042,Volvo 850,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51043,"Volvo 70 Series (For XC70 for 2014 on, use model code 402)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51044,Volvo 90 Series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51045,Volvo 80 Series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51046,Volvo 40 Series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51047,Volvo 60 Series,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51048,Volvo V50,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51049,Volvo C30,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51050,Volvo XC60,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51051,Volvo V60,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51398,Volvo Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51399,Volvo Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51401,Volvo XC90,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51402,"Volvo XC70 (For 2014 on.  For prior to 2013, use model code 043)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51499,Volvo Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51881,Volvo Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51882,Volvo Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51883,Volvo Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51884,Volvo Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51890,Volvo Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51898,Volvo Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51981,Volvo Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51988,Volvo Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51989,Volvo Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51998,Volvo Other (Vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51999,Volvo Unknown (VOLVO),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52031,Mitsubishi Starion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52032,Mitsubishi Tredia,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52033,Mitsubishi Cordia,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52034,Mitsubishi Galant,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52035,Mitsubishi Mirage (For 1985-2002.  For 2014 on use model 048.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52036,Mitsubishi Precis,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52037,Mitsubishi Eclipse,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52038,Mitsubishi Sigma,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52039,Mitsubishi 3000 GT,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52040,Mitsubishi Diamante,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52041,Mitsubishi iMEV,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52045,Mitsubishi Expo Wagon,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52046,Mitsubishi Lancer/Lancer Sportback/ Lancer Evolution,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52047,Mitsubishi Outlander,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52048,Mitsubishi Mirage (2014 on.  For 1985-2002 use 52-035.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52398,Mitsubishi Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52399,Mitsubishi Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52401,Mitsubishi Montero/Montero Sport,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52402,Mitsubishi Endeavor,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52441,Mitsubishi Mini-Van,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52471,Mitsubishi Pickup,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52472,Mitsubishi Raider,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52498,Mitsubishi Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52499,Mitsubishi Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52882,"Mitsubishi Medium/Heavy - COE, low entry",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52898,Mitsubishi Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52981,Mitsubishi Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52982,"Mitsubishi Bus: Front engine, Flat Front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52983,"Mitsubishi Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52988,Mitsubishi Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52989,Mitsubishi Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52999,Mitsubishi Unknown (MITSUBISHI),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53031,Suzuki Swift/SA310,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53032,Suzuki Esteem,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53033,Suzuki Aerio,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53034,Suzuki Forenza,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53035,Suzuki Verona,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53036,Suzuki Reno,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53040,Suzuki SX4/SX4 Crossover,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53041,Suzuki Kizashi,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53398,Suzuki Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53399,Suzuki Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53401,Suzuki Samurai,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53402,Suzuki Sidekick/Vitara/ Vitara V6,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53403,Suzuki X-90,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53404,Suzuki Grand Vitara (2003 on; see model 402 for models prior to 2003),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53405,Suzuki XL-7 (2003 on; see 402 for 2002 model year),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53481,Suzuki Equator,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53498,Suzuki Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53499,Suzuki Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53701,Suzuki 0-50cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53702,Suzuki 51-124cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53703,Suzuki 125-349cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53704,Suzuki 350-449cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53705,Suzuki 450-749cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53706,Suzuki 750cc-over,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53709,Suzuki Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53731,Suzuki 0-50cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53732,Suzuki 51-124cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53733,Suzuki 125-349cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53734,Suzuki 350cc or greater (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53739,Suzuki Unknown cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53999,Suzuki Unknown (SUZUKI),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54031,Acura Integra,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54032,Acura Legend,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54033,Acura NSX (For 1991-2005 only.  For 2016 on see model 043.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54034,Acura Vigor,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54035,Acura TL,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54036,Acura RL/RLX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54037,Acura CL,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54038,Acura RSX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54039,Acura TSX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54040,Acura ZDX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54041,Acura ILX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54044,Acura TLX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54398,Acura Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54399,Acura Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54401,Acura SLX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54402,Acura RDX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54421,Acura MDX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54499,Acura Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54999,Acura Unknown (ACURA),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55031,Hyundai Pony,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55032,Hyundai Excel,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55033,Hyundai Sonata,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55034,Hyundai Scoupe,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55035,Hyundai Elantra,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55036,Hyundai Accent,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55037,Hyundai Tiburon,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55038,Hyundai XG300(2001)/ XG350(2002 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55039,Hyundai Azera,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55040,Hyundai Equus,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55041,Hyundai Genesis,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55042,Hyundai Veloster,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55398,Hyundai Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55399,Hyundai Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55401,Hyundai Santa Fe,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55402,Hyundai Tucson,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55403,Hyundai Veracruz (2007 only),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55421,Hyundai Veracruz  (2008 on; see 403 for 2007 only),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55441,Hyundai Entourage,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55499,Hyundai Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55999,Hyundai Unknown (HYUNDAI),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",56031,Merkur XR4Ti,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",56032,Merkur Scorpio,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",56398,Merkur Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",56399,Merkur Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",57031,Yugo GV/GVL/GVX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58031,Infiniti M30,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58032,Infiniti Q45,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58033,Infiniti G20,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58034,Infiniti J30,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58035,Infiniti I30,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58036,Infiniti I35,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58037,Infiniti G25/G35/G37,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58038,Infiniti M35/M37/M45/M56,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58039,Infiniti FX35/FX37/FX45/FX50,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58040,Infiniti EX35/EX37,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58041,Infiniti Q50,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58042,Infiniti Q60,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58043,Infiniti Q70,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58044,Infiniti QX50,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58398,Infiniti Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58399,Infiniti Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58401,Infiniti QX4,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58402,Infiniti JX35,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58403,Infiniti QX60,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58404,Infiniti QX70,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58421,Infiniti QX56,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58422,Infiniti QX80,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58499,Infiniti Unknown (Light Truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58999,Infiniti Unknown (INFINITI),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59031,Lexus ES-250/300/300h/330/ 350,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59032,Lexus LS-400/430/460/L/600h/L,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59033,Lexus SC-400/SC-300,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59034,Lexus GS-300/350/400/430/ 450h/460,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59035,Lexus IS-250/300/350/500,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59036,Lexus SC-430,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59037,Lexus HS 250h,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59038,Lexus CT 200h,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59039,Lexus LFA,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59040,Lexus RC,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59398,Lexus Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59399,Lexus Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59401,Lexus RX300/350,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59402,Lexus GX470,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59403,Lexus RX330/400h,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59404,Lexus GX460,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59405,Lexus NX,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59421,Lexus LX450/470/570,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59499,Lexus Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59999,Lexus Unknown (LEXUS),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",60031,Daihatsu Charade,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",60401,Daihatsu Rocky,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",60999,Daihatsu Unknown (DAIHATSU),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",61031,Sterling 827,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",61398,Sterling Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",61399,Sterling Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62401,Land Rover Discovery,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62402,Land Rover Defender,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62403,Land Rover Freelander (2004 on; see 422 for 2002-03.),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62404,Land Rover Range Rover Evoque,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62405,Land Rover Discovery Sport,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62421,Land Rover Range Rover,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62422,Land Rover Freelander (2002-03 only; see 403 for 2004 on),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62423,Land Rover LR3/LR4,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62424,Land Rover LR2,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62498,Land Rover Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62499,Land Rover Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63031,KIA Sephia,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63032,KIA Rio/Rio5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63033,KIA Spectra/Spectra5,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63034,KIA Optima,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63035,KIA Amanti,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63036,KIA Rondo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63037,KIA Soul,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63038,KIA Forte,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63039,KIA Cadenza,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63040,KIA K900,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63398,KIA Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63399,KIA Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63401,KIA Sportage,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63402,KIA Sorrento,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63421,KIA Borrego,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63441,KIA Sedona,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63498,KIA Other (Light Truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63499,KIA Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63999,KIA Unknown (KIA),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",64031,Daewoo Lanos,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",64032,Daewoo Nubira,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",64033,Daewoo Leganza,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",64398,Daewoo Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",64399,Daewoo Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",65031,Smart Fortwo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",65398,Smart Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",65399,Smart Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67031,Scion xB (2012 on.  See Toyota for 2004-2011),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67032,Scion tC (2012 on.  See Toyota for 2005-2011),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67033,Scion xD (2012 on.  See Toyota for 2007-2011),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67034,Scion iQ (2012 on.  See Toyota for 2010-2011),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67035,Scion FR-S,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67398,Scion Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67399,Scion Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69031,Other Import Aston Martin,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69032,Other Import Bricklin,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69033,Other Import Citroen,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69034,Other Import DeLorean,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69035,Other Import Ferrari,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69036,Other Import Hillman,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69037,Other Import Jensen,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69038,Other Import Lamborghini,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69039,Other Import Lotus,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69040,Other Import Maserati,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69041,Other Import Morris,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69042,Other Import Rolls Royce/Bentley,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69044,Other Import Simca,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69045,Other Import Sunbeam,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69046,Other Import TVR,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69048,Other Import Desta,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69049,Other Import Reliant,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69052,Other Import Bertone,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69053,Other Import Lada,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69054,Other Import Mini-Cooper,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69055,Other Import Morgan (2003 on; Prior to 2003 see 398),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69056,Other Import Maybach,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69057,Other Import Spyker,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69058,Other Import Koenigsegg,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69061,Other Import Mahindra,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69062,Other Import Caterhan,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69063,Other Import McLaren,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69064,Other Import Bugatti,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69398,Other Import Other (automotive),1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69399,Other Import Unknown Make,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70701,BSA 0-50cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70702,BSA 51-124cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70703,BSA 125-349cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70704,BSA 350-449cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70705,BSA 450-749cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70706,BSA 750cc or greater,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70709,BSA Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71701,Ducati 0-50cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71702,Ducati 51-124cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71703,Ducati 125-349cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71704,Ducati 350-449cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71705,Ducati 450-749cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71706,Ducati 750cc or greater,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71709,Ducati Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72701,Harley-Davidson 0-50cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72702,Harley-Davidson 51-124cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72703,Harley-Davidson 125-349cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72704,Harley-Davidson 350-449cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72705,Harley-Davidson 450-749cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72706,Harley-Davidson 750cc or greater,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72709,Harley-Davidson Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73701,Kawasaki 0-50cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73702,Kawasaki 51-124cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73703,Kawasaki 125-349cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73704,Kawasaki 350-449cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73705,Kawasaki 450-749cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73706,Kawasaki 750cc or greater,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73709,Kawasaki Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73731,Kawasaki 0-50cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73732,Kawasaki 51-124cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73733,Kawasaki 125-349cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73734,Kawasaki 350cc or greater (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73739,Kawasaki Unknown cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73998,Kawasaki Other (Vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",74704,Moto-Guzzi 350-449cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",74705,Moto-Guzzi 450-749cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",74706,Moto-Guzzi 750cc or greater,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",74709,Moto-Guzzi Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",75704,Norton 350-449cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",75705,Norton 450-749cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",75706,Norton 750cc or greater,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",75709,Norton Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76701,Yamaha 0-50cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76702,Yamaha 51-124cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76703,Yamaha 125-349cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76704,Yamaha 350-449cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76705,Yamaha 450-749cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76706,Yamaha 750cc or greater,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76709,Yamaha Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76731,Yamaha 0-50cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76732,Yamaha 51-124cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76733,Yamaha 125-349cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76734,Yamaha 350cc or greater (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76739,Yamaha Unknown cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76998,Yamaha Other (Vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",77706,Victory 750cc or greater,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",77709,Victory Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",77998,Victory Other (Vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80850,Brockway Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80881,Brockway Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80882,Brockway Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80883,Brockway Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80884,Brockway Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80890,Brockway Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80898,Brockway Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80981,Brockway Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80982,"Brockway Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80983,"Brockway Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80988,Brockway Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80989,Brockway Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80998,Brockway Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80999,Brockway Unknown (BROCKWAY),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81850,Diamond Reo/Reo Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81881,Diamond Reo/Reo Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81882,Diamond Reo/Reo Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81883,Diamond Reo/Reo Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81884,Diamond Reo/Reo Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81890,Diamond Reo/Reo Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81898,Diamond Reo/Reo Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81981,Diamond Reo/Reo Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81982,"Diamond Reo/Reo Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81983,"Diamond Reo/Reo Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81988,Diamond Reo/Reo Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81989,Diamond Reo/Reo Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81998,Diamond Reo/Reo Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81999,Diamond Reo/Reo Unknown (DIAMOND REO or REO),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82461,Freightliner Sprinter/Advantage,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82462,Freightliner MT 35 Chassis,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82498,Freightliner Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82499,Freightliner Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82850,Freightliner Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82870,Freightliner Medium Heavy Van-Based Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82881,Freightliner Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82882,Freightliner Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82883,Freightliner Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82884,Freightliner Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82890,Freightliner Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82898,Freightliner Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82981,Freightliner Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82982,"Freightliner Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82983,"Freightliner Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82988,Freightliner Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82989,Freightliner Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82998,Freightliner Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82999,Freightliner Unknown (FREIGHTLINER),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83850,FWD Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83881,FWD Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83882,FWD Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83883,FWD Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83884,FWD Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83890,FWD Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83898,FWD Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83981,FWD Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83982,"FWD Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83983,"FWD Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83988,FWD Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83989,FWD Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83998,FWD Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83999,FWD Unknown (FWD),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84421,International Harvester/Navistar Scout,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84431,International Harvester/Navistar Travelall,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84466,International Harvester/Navistar Multistop Van,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84481,International Harvester/Navistar Pickup,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84498,International Harvester/Navistar Other light truck,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84499,International Harvester/Navistar Unknown light truck,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84850,International Harvester/Navistar Motorhome,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84881,International Harvester/Navistar Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84882,International Harvester/Navistar Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84883,International Harvester/Navistar Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84884,International Harvester/Navistar Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84890,International Harvester/Navistar Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84898,International Harvester/Navistar Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84981,International Harvester/Navistar Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84982,"International Harvester/Navistar Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84983,"International Harvester/Navistar Bus**: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84988,International Harvester/Navistar Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84989,International Harvester/Navistar Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84998,International Harvester/Navistar Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84999,International Harvester/Navistar Unknown (INTL. HARVESTER/ NAVISTAR),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85850,Kenworth Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85881,Kenworth Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85882,Kenworth Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85883,Kenworth Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85884,Kenworth Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85890,Kenworth Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85898,Kenworth Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85981,Kenworth Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85982,"Kenworth Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85983,"Kenworth Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85988,Kenworth Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85989,Kenworth Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85998,Kenworth Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85999,Kenworth Unknown (KENWORTH),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86850,Mack Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86881,Mack Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86882,Mack Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86883,Mack Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86884,Mack Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86890,Mack Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86898,Mack Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86981,Mack Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86982,"Mack Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86983,"Mack Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86988,Mack Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86989,Mack Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86998,Mack Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86999,Mack Unknown (MACK),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87850,Peterbilt Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87881,Peterbilt Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87882,Peterbilt Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87883,Peterbilt Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87884,Peterbilt Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87890,Peterbilt Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87898,Peterbilt Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87981,Peterbilt Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87982,"Peterbilt Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87983,"Peterbilt Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87988,Peterbilt Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87989,Peterbilt Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87998,Peterbilt Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87999,Peterbilt Unknown (PETERBILT),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88850,Iveco/Magirus Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88881,Iveco/Magirus Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88882,Iveco/Magirus Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88883,Iveco/Magirus Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88884,Iveco/Magirus Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88890,Iveco/Magirus Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88898,Iveco/Magirus Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88981,Iveco/Magirus Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88982,"Iveco/Magirus Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88983,"Iveco/Magirus Bus: Rear engine,Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88988,Iveco/Magirus Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88989,Iveco/Magirus Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88998,Iveco/Magirus Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88999,Iveco/Magirus Unknown (IVECO/MAGIRUS),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89850,White/Autocar White/GMC Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89881,White/Autocar White/GMC Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89882,White/Autocar White/GMC Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89883,White/Autocar White/GMC Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89884,White/Autocar White/GMC Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89890,White/Autocar White/GMC Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89898,White/Autocar White/GMC Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89981,White/Autocar White/GMC Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89982,"White/Autocar White/GMC Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89983,"White/Autocar White/GMC Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89988,White/Autocar White/GMC Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89989,White/Autocar White/GMC Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89998,White/Autocar White/GMC Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89999,White/Autocar White/GMC Unknown (WHITE/AUTOCAR-WHITE/GMC),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90461,Bluebird Van Based,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90981,Bluebird Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90982,"Bluebird Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90983,"Bluebird Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90988,Bluebird Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90989,Bluebird Unknown (Bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90999,Bluebird Unknown (BLUEBIRD),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",91981,Eagle Coach Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",91982,"Eagle Coach Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",91983,"Eagle Coach Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",91988,Eagle Coach Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",91989,Eagle Coach Unknown (Bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",92981,Gillig Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",92982,"Gillig Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",92983,"Gillig Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",92988,Gillig Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",92989,Gillig Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",93981,MCI Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",93982,"MCI Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",93983,"MCI Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",93988,MCI Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",93989,MCI Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94461,Thomas Built Van Based,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94981,Thomas Built Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94982,"Thomas Built Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94983,"Thomas Built Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94988,Thomas Built Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94989,Thomas Built Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94999,Thomas Built Unknown(THOMAS BUILT),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",97997,Not Reported Not Reported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98301,Other Make Think,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98302,Other Make Meyers Motor,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98398,Other Make Other (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98498,Other Make Other (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98598,Other Make Other (LSV/NEV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98701,Other Make 0-50cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98702,Other Make 51-124cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98703,Other Make 125-349cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98704,Other Make 350-449cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98705,Other Make 450-749cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98706,Other Make 750cc or greater,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98709,Other Make Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98731,Other Make 0-50cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98732,Other Make 51-124cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98733,Other Make 125-349cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98734,Other Make 350cc or greater (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98739,Other Make Unknown cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98802,Other Make Auto-Union-DKW,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98803,Other Make Divco,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98804,Other Make Western Star,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98805,Other Make Oshkosh,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98806,Other Make Hino,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98807,Other Make Scania,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98808,Other Make UD,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98809,Other Make Sterling,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98850,Other Make Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98870,Other Make Medium/Heavy Van-Based Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98881,Other Make Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98882,Other Make Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98883,Other Make Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98884,Other Make Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98890,Other Make Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98898,Other Make Other (medium/heavy truck)**,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98902,Other Make Neoplan,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98903,Other Make Carpenter,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98904,Other Make Collins Bus,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98905,Other Make DINA,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98906,Other Make Mid Bus,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98907,Other Make Orion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98908,Other Make Van Hool,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98981,Other Make Bus***: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98982,"Other Make Bus: Front engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98983,"Other Make Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98988,Other Make Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98998,Other Make Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98999,Other Make Unknown (OTHER MAKE),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99399,Unknown Make Unknown (automobile),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99499,Unknown Make Unknown (light truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99598,Unknown Make Unknown (LSG/NGV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99599,Unknown Make Unknown (LSV/NGV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99701,Unknown Make 0-50cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99702,Unknown Make 51-124cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99703,Unknown Make 125-349cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99704,Unknown Make 350-449cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99705,Unknown Make 450-749cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99706,Unknown Make 750cc or greater,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99709,Unknown Make Unknown cc,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99731,Unknown Make 0-50cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99732,Unknown Make 51-124cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99733,Unknown Make 125-349cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99734,Unknown Make 350cc or greater (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99739,Unknown Make Unknown cc (ATV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99850,Unknown Make Motor Home,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99870,Unknown Make Medium Heavy Van-Based Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99881,Unknown Make Medium/Heavy - CBE,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99882,Unknown Make Medium/Heavy - COE low entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99883,Unknown Make Medium/Heavy - COE high entry,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99884,Unknown Make Medium/Heavy - Unknown engine location,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99890,Unknown Make Medium/Heavy - COE entry position unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99898,Unknown Make Other (medium/heavy truck),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99981,Unknown Make Bus**: Conventional (Engine out front),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99982,Unknown Make Bus: Front engine. Flat front,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99983,"Unknown Make Bus: Rear engine, Flat front",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99988,Unknown Make Other (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99989,Unknown Make Unknown (bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99998,Unknown Make Other (vehicle),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99999,"Unknown Make Unknown (as to automobile, motored cycle, light truck or truck)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",1,"Convertible(excludes sun-roof,t-bar)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",2,"2-door sedan,hardtop,coupe",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",3,3-door/2-door hatchback,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",4,"4-door sedan, hardtop",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",5,5-door/4-door hatchback,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",6,Station Wagon (excluding van and truck based),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",7,"Hatchback, number of doors unknown",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",8,"Sedan/Hardtop, number of doors unknown",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",9,Other or Unknown automobile type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",10,"Auto-based pickup (includes E1 Camino, Caballero, Ranchero, SSR, G8-ST, Subaru Brat, Rabbit Pickup)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",11,"Auto-based panel (cargo station wagon, auto-based ambulance or hearse)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",12,Large Limousine-more than four side doors or stretched chassis,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",13,Three-wheel automobile or automobile derivative,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",14,"Compact Utility (Utility Vehicle Categories ""Small"" and ""Midsize"")",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",15,"Large utility (ANSI D16.1 Utility Vehicle Categories and ""Full Size"" and ""Large"")",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",16,"Utility station wagon (includes suburban limousines, Suburban, Travellall, Grand Wagoneer)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",17,3-door coupe,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",19,"Utility Vehicle, Unknown body type",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",20,"Minivan (Chrysler Town and Country, Caravan, Grand Caravan, Voyager, Voyager, Honda-Odyssey, ...)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",21,"Large Van-Includes van-based buses (B150-B350, Sportsman, Royal Maxiwagon, Ram, Tradesman,...)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",22,"Step-van or walk-in van (<= 10,000 lbs. GVWR)",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",28,"Other van type (Hi-Cube Van, Kary)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",29,Unknown van type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",30,"Compact pickup (GVWR <4,500 lbs.) (D50,Colt P/U, Ram 50, Dakota, Arrow Pickup [foreign], Ranger, ..)",1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",31,"Standard pickup (GVWR 4,500 to 10,00 lbs.)(Jeep Pickup, Comanche, Ram Pickup, D100-D350, ......)",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",32,Pickup with slide-in camper,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",33,Convertible pickup,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",39,Unknown (pickup style) light conventional truck type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",40,"Cab Chassis Based (includes Rescue Vehicle, Light Stake, Dump, and Tow Truck)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",41,Truck based panel,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",42,Light Truck Based Motorhome (Chassis Mounted),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",45,Other light conventional truck type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",48,Unknown light truck type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",49,"Unknown light vehicle type (automobile,utility vehicle, van, or light truck)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",50,School Bus,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",51,Cross Country/Intercity Bus,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",52,Transit Bus (City Bus),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",55,"Van-Based Bus GVWR > 10,000 lbs.",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",58,Other Bus Type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",59,Unknown Bus Type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",60,"Step van (>10,000 lbs. GVWR)",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",61,"Single-unit straight truck or Cab-Chassis (10,000 lbs. < GVWR < or = 19,500 lbs.)",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",62,"Single-unit straight truck or Cab-Chassis (19,500 lbs. < GVWR < or = 26,000 lbs.)",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",63,"Single-unit straight truck or Cab-Chassis (GVWR > 26,000 lbs.)",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",64,Single-unit straight truck or Cab-Chassis (GVWR unknown),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",65,Medium/heavy truck based motorhome,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",66,"Truck-tractor (Cab only, or with any number of trailing unit; any weight)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",67,"Medium/heavy Pickup (>10,000 lbs. GVWR)",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",71,"Unknown if single unit or combination unit Medium Truck (10,000 lbs. < GVWR < 26,000 lbs.)",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",72,"Unknown if single unit or combination unit Heavy Truck (GVWR > 26,000 lbs.)",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",73,"Camper or motorhome, unknown truck type",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",78,Unknown medium/heavy truck type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",79,Unknown truck type (light/medium/heavy),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",80,Motorcycle,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",81,Moped (motorized bicycle),1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",82,Three-wheel Motorcycle or Moped - not All-Terrain Vehicle,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",83,Off-road Motorcycle (2-wheel),1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",88,"Other motored cycle type (mini-bikes, motor scooters, pocket motorcycles, ""pocket bikes"")",1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",89,Unknown motored cycle type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",90,ATV/ATC [All-Terrain Cycle],1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",91,Snowmobile,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",92,Farm equipment other than trucks,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",93,Construction equipment other than trucks (includes graders),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",94,Low Speed Vehicle (LSV) / Neighborhood Electric Vehicle (NEV),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",95,Golf Cart,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",97,"Other vehicle type (includes go-cart, fork-lift, city street sweeper dunes/swamp buggy)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",98,Not Reported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",99,Unknown body type,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MOD_YEAR,mod_year,Vehicle Model Year,This data element identifies the manufacturer’s model year of this vehicle.,Prior to 2020 the Data Element ID was V12. This data element also appears in the Person data file and in the Parkwork data file as PMODYEAR.,9998,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MOD_YEAR,mod_year,Vehicle Model Year,This data element identifies the manufacturer’s model year of this vehicle.,Prior to 2020 the Data Element ID was V12. This data element also appears in the Person data file and in the Parkwork data file as PMODYEAR.,9999,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VIN,vin,Vehicle Identification Number,"This data element records the vehicle identification number (VIN) of this vehicle assigned by the vehicle manufacturer. The VIN contains information on the vehicle such as: manufacturer, model year, model, body type, restraint type, etc.","The vehicle manufacturers use the VIN to describe certain characteristics of a vehicle and to assign a serial number to the vehicle. Starting in 1981 the Vehicle Identification Numbers were required to conform to an international standard. For vehicles built prior to 1981 one may consult the National Automobile Theft Bureau’s publication Passenger Vehicle Identification Manual for the year in question. Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V13. This data element also appears in the Parkwork data file as PVIN.",000000000000,No VIN Required,1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,VIN,vin,Vehicle Identification Number,"This data element records the vehicle identification number (VIN) of this vehicle assigned by the vehicle manufacturer. The VIN contains information on the vehicle such as: manufacturer, model year, model, body type, restraint type, etc.","The vehicle manufacturers use the VIN to describe certain characteristics of a vehicle and to assign a serial number to the vehicle. Starting in 1981 the Vehicle Identification Numbers were required to conform to an international standard. For vehicles built prior to 1981 one may consult the National Automobile Theft Bureau’s publication Passenger Vehicle Identification Manual for the year in question. Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V13. This data element also appears in the Parkwork data file as PVIN.",888888888888,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VIN,vin,Vehicle Identification Number,"This data element records the vehicle identification number (VIN) of this vehicle assigned by the vehicle manufacturer. The VIN contains information on the vehicle such as: manufacturer, model year, model, body type, restraint type, etc.","The vehicle manufacturers use the VIN to describe certain characteristics of a vehicle and to assign a serial number to the vehicle. Starting in 1981 the Vehicle Identification Numbers were required to conform to an international standard. For vehicles built prior to 1981 one may consult the National Automobile Theft Bureau’s publication Passenger Vehicle Identification Manual for the year in question. Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V13. This data element also appears in the Parkwork data file as PVIN.",999999999999,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",0,No Trailing Units,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",1,One Trailing Unit,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",2,Two Trailing Units,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",3,Three or More Trailing Units,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",4,"Yes, Number of Trailing Units Unknown",1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",5,Vehicle Towing Another Motor Vehicle - Fixed Linkage,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",6,Vehicle Towing Another Motor Vehicle - Non-Fixed Linkage,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,J_KNIFE,j_knife,Jackknife,This data element identifies whether this vehicle experienced a jackknife anytime during the unstabilized situation.,"Jackknife applies to a condition that occurs to a combination vehicle while in motion. A Jackknife occurs when there is an uncontrolled articulation between the power unit and the trailer or trailers in which the trailer does not follow directly behind the power unit (tracking), and the driver did not initiate the non-tracking situation. The condition reflects a loss of control of the vehicle by the driver in which the trailer’s normal straight-line path behind the power unit is not maintained. If the final resting configuration of the vehicle is in a jackknife position, it does not necessarily mean that the vehicle has jackknifed. From 1975 to 1979 the data element exists in the data files but has not been initialized. These data were not collected. Prior to 2016 the Data Element ID was V15. From 2016 to 2019 the Data Element ID was V16.",0,Not an Articulated Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,J_KNIFE,j_knife,Jackknife,This data element identifies whether this vehicle experienced a jackknife anytime during the unstabilized situation.,"Jackknife applies to a condition that occurs to a combination vehicle while in motion. A Jackknife occurs when there is an uncontrolled articulation between the power unit and the trailer or trailers in which the trailer does not follow directly behind the power unit (tracking), and the driver did not initiate the non-tracking situation. The condition reflects a loss of control of the vehicle by the driver in which the trailer’s normal straight-line path behind the power unit is not maintained. If the final resting configuration of the vehicle is in a jackknife position, it does not necessarily mean that the vehicle has jackknifed. From 1975 to 1979 the data element exists in the data files but has not been initialized. These data were not collected. Prior to 2016 the Data Element ID was V15. From 2016 to 2019 the Data Element ID was V16.",1,No,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,J_KNIFE,j_knife,Jackknife,This data element identifies whether this vehicle experienced a jackknife anytime during the unstabilized situation.,"Jackknife applies to a condition that occurs to a combination vehicle while in motion. A Jackknife occurs when there is an uncontrolled articulation between the power unit and the trailer or trailers in which the trailer does not follow directly behind the power unit (tracking), and the driver did not initiate the non-tracking situation. The condition reflects a loss of control of the vehicle by the driver in which the trailer’s normal straight-line path behind the power unit is not maintained. If the final resting configuration of the vehicle is in a jackknife position, it does not necessarily mean that the vehicle has jackknifed. From 1975 to 1979 the data element exists in the data files but has not been initialized. These data were not collected. Prior to 2016 the Data Element ID was V15. From 2016 to 2019 the Data Element ID was V16.",2,Yes - First Event,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,J_KNIFE,j_knife,Jackknife,This data element identifies whether this vehicle experienced a jackknife anytime during the unstabilized situation.,"Jackknife applies to a condition that occurs to a combination vehicle while in motion. A Jackknife occurs when there is an uncontrolled articulation between the power unit and the trailer or trailers in which the trailer does not follow directly behind the power unit (tracking), and the driver did not initiate the non-tracking situation. The condition reflects a loss of control of the vehicle by the driver in which the trailer’s normal straight-line path behind the power unit is not maintained. If the final resting configuration of the vehicle is in a jackknife position, it does not necessarily mean that the vehicle has jackknifed. From 1975 to 1979 the data element exists in the data files but has not been initialized. These data were not collected. Prior to 2016 the Data Element ID was V15. From 2016 to 2019 the Data Element ID was V16.",3,Yes - Subsequent Event,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",0,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",3,American Samoa,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",14,Guam,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",57,US DOT,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",58,MC/MX (ICC),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",77,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",88,None,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",95,Canada,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",96,Mexico,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",99,Unknown,1,1,1,1,NA,NA,1,1,1,1
FARS,vehicle,MCARR_I2,mcarr_i2,MCID Identification Number,This data element records the motor carrier identification number if applicable to this vehicle.,"The Carrier Identification Number is found only on vehicles of interstate for-hire or private carriers in the transportation business. It is the unique number assigned to the Carrier by the United States Department of Commerce Commission, or the State. The number can be either a U.S. DOT number (on interstate private carriers) or an ICC MC number (interstate for-hire carriers). Collected only for buses and trucks over 4,500 kg GVWR, this data element is applicable to the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •    Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)         greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16B. From 2016 to 2019 the Data Element ID was V17B. This data element also appears in the Parkwork data file as PMCARR_I2.",000000000,Not Applicable,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MCARR_I2,mcarr_i2,MCID Identification Number,This data element records the motor carrier identification number if applicable to this vehicle.,"The Carrier Identification Number is found only on vehicles of interstate for-hire or private carriers in the transportation business. It is the unique number assigned to the Carrier by the United States Department of Commerce Commission, or the State. The number can be either a U.S. DOT number (on interstate private carriers) or an ICC MC number (interstate for-hire carriers). Collected only for buses and trucks over 4,500 kg GVWR, this data element is applicable to the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •    Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)         greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16B. From 2016 to 2019 the Data Element ID was V17B. This data element also appears in the Parkwork data file as PMCARR_I2.",777777777,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I2,mcarr_i2,MCID Identification Number,This data element records the motor carrier identification number if applicable to this vehicle.,"The Carrier Identification Number is found only on vehicles of interstate for-hire or private carriers in the transportation business. It is the unique number assigned to the Carrier by the United States Department of Commerce Commission, or the State. The number can be either a U.S. DOT number (on interstate private carriers) or an ICC MC number (interstate for-hire carriers). Collected only for buses and trucks over 4,500 kg GVWR, this data element is applicable to the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •    Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)         greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16B. From 2016 to 2019 the Data Element ID was V17B. This data element also appears in the Parkwork data file as PMCARR_I2.",888888888,None,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_I2,mcarr_i2,MCID Identification Number,This data element records the motor carrier identification number if applicable to this vehicle.,"The Carrier Identification Number is found only on vehicles of interstate for-hire or private carriers in the transportation business. It is the unique number assigned to the Carrier by the United States Department of Commerce Commission, or the State. The number can be either a U.S. DOT number (on interstate private carriers) or an ICC MC number (interstate for-hire carriers). Collected only for buses and trucks over 4,500 kg GVWR, this data element is applicable to the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •    Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)         greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16B. From 2016 to 2019 the Data Element ID was V17B. This data element also appears in the Parkwork data file as PMCARR_I2.",999999999,Unknown,1,1,1,1,NA,NA,1,1,1,1
FARS,vehicle,MCARR_ID,mcarr_id,Motor Carrier Identification Number,This data element records the issuing authority and motor carrier identification number (if applicable) to this vehicle.,"This 11-character data element is the combination of two data elements, the two-digit “Motor Carrier Issuing Authority” code (MCARR_I1) followed by the nine-character “Identification Number” (MCARR_I2). The Carrier Identification Number is found only on vehicles of interstate for-hire or private carriers in the transportation business. It is the unique number assigned to the Carrier by the United States Department of Commerce Commission or the State. The number can be either a U.S. DOT number (on interstate private carriers) or an ICC MC number (interstate for-hire carriers). Collected only for buses and trucks over 4,500 kg GVWR, this data element is applicable to the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver)    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16. From 2016 to 2019 the Data Element ID was V17. This data element also appears in the Parkwork data file as PMCARR_ID.",00000000000,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_ID,mcarr_id,Motor Carrier Identification Number,This data element records the issuing authority and motor carrier identification number (if applicable) to this vehicle.,"This 11-character data element is the combination of two data elements, the two-digit “Motor Carrier Issuing Authority” code (MCARR_I1) followed by the nine-character “Identification Number” (MCARR_I2). The Carrier Identification Number is found only on vehicles of interstate for-hire or private carriers in the transportation business. It is the unique number assigned to the Carrier by the United States Department of Commerce Commission or the State. The number can be either a U.S. DOT number (on interstate private carriers) or an ICC MC number (interstate for-hire carriers). Collected only for buses and trucks over 4,500 kg GVWR, this data element is applicable to the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver)    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16. From 2016 to 2019 the Data Element ID was V17. This data element also appears in the Parkwork data file as PMCARR_ID.",77777777777,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_ID,mcarr_id,Motor Carrier Identification Number,This data element records the issuing authority and motor carrier identification number (if applicable) to this vehicle.,"This 11-character data element is the combination of two data elements, the two-digit “Motor Carrier Issuing Authority” code (MCARR_I1) followed by the nine-character “Identification Number” (MCARR_I2). The Carrier Identification Number is found only on vehicles of interstate for-hire or private carriers in the transportation business. It is the unique number assigned to the Carrier by the United States Department of Commerce Commission or the State. The number can be either a U.S. DOT number (on interstate private carriers) or an ICC MC number (interstate for-hire carriers). Collected only for buses and trucks over 4,500 kg GVWR, this data element is applicable to the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver)    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16. From 2016 to 2019 the Data Element ID was V17. This data element also appears in the Parkwork data file as PMCARR_ID.",88888888888,None,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,MCARR_ID,mcarr_id,Motor Carrier Identification Number,This data element records the issuing authority and motor carrier identification number (if applicable) to this vehicle.,"This 11-character data element is the combination of two data elements, the two-digit “Motor Carrier Issuing Authority” code (MCARR_I1) followed by the nine-character “Identification Number” (MCARR_I2). The Carrier Identification Number is found only on vehicles of interstate for-hire or private carriers in the transportation business. It is the unique number assigned to the Carrier by the United States Department of Commerce Commission or the State. The number can be either a U.S. DOT number (on interstate private carriers) or an ICC MC number (interstate for-hire carriers). Collected only for buses and trucks over 4,500 kg GVWR, this data element is applicable to the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver)    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16. From 2016 to 2019 the Data Element ID was V17. This data element also appears in the Parkwork data file as PMCARR_ID.",99999999999,Unknown,1,1,1,1,NA,NA,1,1,1,1
FARS,vehicle,GVWR,gvwr,Gross Vehicle Weight Rating,This data element identifies the gross vehicle weight rating of this vehicle if applicable.,"The gross vehicle weight rating (GVWR) or gross combination weight rating (GCWR) is a value specified by the manufacturer for a single-unit truck, truck tractor, or trailer. In the absence of a gross vehicle weight rating, an estimate of the gross weight of a fully loaded unit can be substituted. In 2000 the GVWR was the sum of the weight of the power unit and its trailers. Since 2001 this data element is the gross vehicle weight of the power unit only. The weight of trailers is not added. Prior to 2016 the Data Element ID was V17. Beginning in 2020 this data element is replaced by two data elements, Power Unit GVWR and Trailer GVWR, which are derived from their VINs. This data element also appears in the Parkwork data file as PGVWR.",0,Not Applicable,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,GVWR,gvwr,Gross Vehicle Weight Rating,This data element identifies the gross vehicle weight rating of this vehicle if applicable.,"The gross vehicle weight rating (GVWR) or gross combination weight rating (GCWR) is a value specified by the manufacturer for a single-unit truck, truck tractor, or trailer. In the absence of a gross vehicle weight rating, an estimate of the gross weight of a fully loaded unit can be substituted. In 2000 the GVWR was the sum of the weight of the power unit and its trailers. Since 2001 this data element is the gross vehicle weight of the power unit only. The weight of trailers is not added. Prior to 2016 the Data Element ID was V17. Beginning in 2020 this data element is replaced by two data elements, Power Unit GVWR and Trailer GVWR, which are derived from their VINs. This data element also appears in the Parkwork data file as PGVWR.",1,"10,000 lbs. or less",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,GVWR,gvwr,Gross Vehicle Weight Rating,This data element identifies the gross vehicle weight rating of this vehicle if applicable.,"The gross vehicle weight rating (GVWR) or gross combination weight rating (GCWR) is a value specified by the manufacturer for a single-unit truck, truck tractor, or trailer. In the absence of a gross vehicle weight rating, an estimate of the gross weight of a fully loaded unit can be substituted. In 2000 the GVWR was the sum of the weight of the power unit and its trailers. Since 2001 this data element is the gross vehicle weight of the power unit only. The weight of trailers is not added. Prior to 2016 the Data Element ID was V17. Beginning in 2020 this data element is replaced by two data elements, Power Unit GVWR and Trailer GVWR, which are derived from their VINs. This data element also appears in the Parkwork data file as PGVWR.",2,"10,001 lbs - 26,000 lbs",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,GVWR,gvwr,Gross Vehicle Weight Rating,This data element identifies the gross vehicle weight rating of this vehicle if applicable.,"The gross vehicle weight rating (GVWR) or gross combination weight rating (GCWR) is a value specified by the manufacturer for a single-unit truck, truck tractor, or trailer. In the absence of a gross vehicle weight rating, an estimate of the gross weight of a fully loaded unit can be substituted. In 2000 the GVWR was the sum of the weight of the power unit and its trailers. Since 2001 this data element is the gross vehicle weight of the power unit only. The weight of trailers is not added. Prior to 2016 the Data Element ID was V17. Beginning in 2020 this data element is replaced by two data elements, Power Unit GVWR and Trailer GVWR, which are derived from their VINs. This data element also appears in the Parkwork data file as PGVWR.",3,"26,001 lbs. or more",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,GVWR,gvwr,Gross Vehicle Weight Rating,This data element identifies the gross vehicle weight rating of this vehicle if applicable.,"The gross vehicle weight rating (GVWR) or gross combination weight rating (GCWR) is a value specified by the manufacturer for a single-unit truck, truck tractor, or trailer. In the absence of a gross vehicle weight rating, an estimate of the gross weight of a fully loaded unit can be substituted. In 2000 the GVWR was the sum of the weight of the power unit and its trailers. Since 2001 this data element is the gross vehicle weight of the power unit only. The weight of trailers is not added. Prior to 2016 the Data Element ID was V17. Beginning in 2020 this data element is replaced by two data elements, Power Unit GVWR and Trailer GVWR, which are derived from their VINs. This data element also appears in the Parkwork data file as PGVWR.",8,Not Reported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,GVWR,gvwr,Gross Vehicle Weight Rating,This data element identifies the gross vehicle weight rating of this vehicle if applicable.,"The gross vehicle weight rating (GVWR) or gross combination weight rating (GCWR) is a value specified by the manufacturer for a single-unit truck, truck tractor, or trailer. In the absence of a gross vehicle weight rating, an estimate of the gross weight of a fully loaded unit can be substituted. In 2000 the GVWR was the sum of the weight of the power unit and its trailers. Since 2001 this data element is the gross vehicle weight of the power unit only. The weight of trailers is not added. Prior to 2016 the Data Element ID was V17. Beginning in 2020 this data element is replaced by two data elements, Power Unit GVWR and Trailer GVWR, which are derived from their VINs. This data element also appears in the Parkwork data file as PGVWR.",9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,0,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,1,"Single-Unit Truck (2- axle and GVWR more than 10,000 lbs)",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,2,Single-Unit Truck (3 or more axles),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,4,Truck Pulling Trailer(s),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,5,Truck Tractor (Bobtail),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,6,Truck Tractor/Semi-Trailer,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,7,Truck Tractor/Double,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,8,Truck Tractor/Triple,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,10,"Vehicle 10,000 pounds or less placarded for hazardous materials",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,19,"Truck More Than 10,000 lbs, Cannot Classify",1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,20,"Bus/Large Van (seats for 9-15 occupants, including driver)",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,21,"Bus (seats for more than 15 occupants, including driver)",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,99,Unknown,1,1,1,1,NA,NA,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,0,Not Applicable (N/A),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,1,Van/Enclosed Box,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,2,Cargo Tank,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,3,Flatbed,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,4,Dump,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,5,Concrete Mixer,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,6,Auto Transporter,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,7,Garbage/Refuse,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,8,Grain/ Chips/ Gravel,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,9,Pole-Trailer,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,10,Log,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,11,Intermodal Container Chassis,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,12,Vehicle Towing Another Motor Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,22,Bus,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,96,No Cargo Body Type,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,97,Other,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,98,Unknown Cargo Body Type,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,99,Unknown,1,1,1,1,NA,NA,1,1,1,1
FARS,vehicle,HAZ_INV,haz_inv,Hazardous Materials Involvement/Placard-HM1 -Involvement,This data element identifies whether this vehicle was carrying hazardous materials.,Prior to 2016 the Data Element ID was V20A/HM1. From 2016 to 2019 the Data Element ID was V21A/HM1. This data element also appears in the Parkwork data file as PHAZ_INV.,1,No,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_INV,haz_inv,Hazardous Materials Involvement/Placard-HM1 -Involvement,This data element identifies whether this vehicle was carrying hazardous materials.,Prior to 2016 the Data Element ID was V20A/HM1. From 2016 to 2019 the Data Element ID was V21A/HM1. This data element also appears in the Parkwork data file as PHAZ_INV.,2,Yes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_PLAC,haz_plac,Hazardous Materials Involvement/Placard-HM2 Placard,This data element identifies the presence of hazardous materials for this vehicle and whether this vehicle displayed a hazardous materials placard.,Prior to 2016 the Data Element ID was V20B/HM2. From 2016 to 2019 the Data Element ID was V21B/HM2. This data element also appears in the Parkwork data file as PHAZPLAC.,0,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_PLAC,haz_plac,Hazardous Materials Involvement/Placard-HM2 Placard,This data element identifies the presence of hazardous materials for this vehicle and whether this vehicle displayed a hazardous materials placard.,Prior to 2016 the Data Element ID was V20B/HM2. From 2016 to 2019 the Data Element ID was V21B/HM2. This data element also appears in the Parkwork data file as PHAZPLAC.,1,No,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_PLAC,haz_plac,Hazardous Materials Involvement/Placard-HM2 Placard,This data element identifies the presence of hazardous materials for this vehicle and whether this vehicle displayed a hazardous materials placard.,Prior to 2016 the Data Element ID was V20B/HM2. From 2016 to 2019 the Data Element ID was V21B/HM2. This data element also appears in the Parkwork data file as PHAZPLAC.,2,Yes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_PLAC,haz_plac,Hazardous Materials Involvement/Placard-HM2 Placard,This data element identifies the presence of hazardous materials for this vehicle and whether this vehicle displayed a hazardous materials placard.,Prior to 2016 the Data Element ID was V20B/HM2. From 2016 to 2019 the Data Element ID was V21B/HM2. This data element also appears in the Parkwork data file as PHAZPLAC.,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_ID,haz_id,Hazardous Materials Involvement/Placard- HM3 Identification Number,This data element identifies the four-digit hazardous materials identification number for this vehicle.,Prior to 2016 the Data Element ID was V20C/HM3. From 2016 to 2019 the Data Element ID was V21C/HM3. This data element also appears in the Parkwork data file as PHAZ_ID.,0,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_ID,haz_id,Hazardous Materials Involvement/Placard- HM3 Identification Number,This data element identifies the four-digit hazardous materials identification number for this vehicle.,Prior to 2016 the Data Element ID was V20C/HM3. From 2016 to 2019 the Data Element ID was V21C/HM3. This data element also appears in the Parkwork data file as PHAZ_ID.,8888,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_CNO,haz_cno,Hazardous Materials Involvement/Placard-HM4 Class Number,This data element identifies the single-digit hazardous materials class number for this vehicle.,Prior to 2016 the Data Element ID was V20D/HM4. From 2016 to 2019 the Data Element ID was V21D/HM4. This data element also appears in the Parkwork data file as PHAZ_CNO.,0,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_CNO,haz_cno,Hazardous Materials Involvement/Placard-HM4 Class Number,This data element identifies the single-digit hazardous materials class number for this vehicle.,Prior to 2016 the Data Element ID was V20D/HM4. From 2016 to 2019 the Data Element ID was V21D/HM4. This data element also appears in the Parkwork data file as PHAZ_CNO.,1,01,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_CNO,haz_cno,Hazardous Materials Involvement/Placard-HM4 Class Number,This data element identifies the single-digit hazardous materials class number for this vehicle.,Prior to 2016 the Data Element ID was V20D/HM4. From 2016 to 2019 the Data Element ID was V21D/HM4. This data element also appears in the Parkwork data file as PHAZ_CNO.,2,02,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_CNO,haz_cno,Hazardous Materials Involvement/Placard-HM4 Class Number,This data element identifies the single-digit hazardous materials class number for this vehicle.,Prior to 2016 the Data Element ID was V20D/HM4. From 2016 to 2019 the Data Element ID was V21D/HM4. This data element also appears in the Parkwork data file as PHAZ_CNO.,3,03,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_CNO,haz_cno,Hazardous Materials Involvement/Placard-HM4 Class Number,This data element identifies the single-digit hazardous materials class number for this vehicle.,Prior to 2016 the Data Element ID was V20D/HM4. From 2016 to 2019 the Data Element ID was V21D/HM4. This data element also appears in the Parkwork data file as PHAZ_CNO.,4,04,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_CNO,haz_cno,Hazardous Materials Involvement/Placard-HM4 Class Number,This data element identifies the single-digit hazardous materials class number for this vehicle.,Prior to 2016 the Data Element ID was V20D/HM4. From 2016 to 2019 the Data Element ID was V21D/HM4. This data element also appears in the Parkwork data file as PHAZ_CNO.,5,05,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_CNO,haz_cno,Hazardous Materials Involvement/Placard-HM4 Class Number,This data element identifies the single-digit hazardous materials class number for this vehicle.,Prior to 2016 the Data Element ID was V20D/HM4. From 2016 to 2019 the Data Element ID was V21D/HM4. This data element also appears in the Parkwork data file as PHAZ_CNO.,6,06,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_CNO,haz_cno,Hazardous Materials Involvement/Placard-HM4 Class Number,This data element identifies the single-digit hazardous materials class number for this vehicle.,Prior to 2016 the Data Element ID was V20D/HM4. From 2016 to 2019 the Data Element ID was V21D/HM4. This data element also appears in the Parkwork data file as PHAZ_CNO.,7,07,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_CNO,haz_cno,Hazardous Materials Involvement/Placard-HM4 Class Number,This data element identifies the single-digit hazardous materials class number for this vehicle.,Prior to 2016 the Data Element ID was V20D/HM4. From 2016 to 2019 the Data Element ID was V21D/HM4. This data element also appears in the Parkwork data file as PHAZ_CNO.,8,08,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_CNO,haz_cno,Hazardous Materials Involvement/Placard-HM4 Class Number,This data element identifies the single-digit hazardous materials class number for this vehicle.,Prior to 2016 the Data Element ID was V20D/HM4. From 2016 to 2019 the Data Element ID was V21D/HM4. This data element also appears in the Parkwork data file as PHAZ_CNO.,9,09,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_CNO,haz_cno,Hazardous Materials Involvement/Placard-HM4 Class Number,This data element identifies the single-digit hazardous materials class number for this vehicle.,Prior to 2016 the Data Element ID was V20D/HM4. From 2016 to 2019 the Data Element ID was V21D/HM4. This data element also appears in the Parkwork data file as PHAZ_CNO.,88,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_REL,haz_rel,Hazardous Materials Involvement/Placard-HM5 Released,This data element identifies whether any hazardous cargo was released from the cargo tank or compartment of this vehicle.,Prior to 2016 the Data Element ID was V20E/HM5. From 2016 to 2019 the Data Element ID was V21E/HM5. This data element also appears in the Parkwork data file as PHAZ_REL.,0,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_REL,haz_rel,Hazardous Materials Involvement/Placard-HM5 Released,This data element identifies whether any hazardous cargo was released from the cargo tank or compartment of this vehicle.,Prior to 2016 the Data Element ID was V20E/HM5. From 2016 to 2019 the Data Element ID was V21E/HM5. This data element also appears in the Parkwork data file as PHAZ_REL.,1,No,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_REL,haz_rel,Hazardous Materials Involvement/Placard-HM5 Released,This data element identifies whether any hazardous cargo was released from the cargo tank or compartment of this vehicle.,Prior to 2016 the Data Element ID was V20E/HM5. From 2016 to 2019 the Data Element ID was V21E/HM5. This data element also appears in the Parkwork data file as PHAZ_REL.,2,Yes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,HAZ_REL,haz_rel,Hazardous Materials Involvement/Placard-HM5 Released,This data element identifies whether any hazardous cargo was released from the cargo tank or compartment of this vehicle.,Prior to 2016 the Data Element ID was V20E/HM5. From 2016 to 2019 the Data Element ID was V21E/HM5. This data element also appears in the Parkwork data file as PHAZ_REL.,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,BUS_USE,bus_use,Bus Use,This data element describes the common type of bus service this vehicle was being used as at the time of the crash or the primary use for the bus if not in service at the time of the crash.,Prior to 2016 the Data Element ID was V21. From 2016 to 2019 the Data Element ID was V22. This data element also appears in the Parkwork data file as PBUS_USE.,0,Not a Bus,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,BUS_USE,bus_use,Bus Use,This data element describes the common type of bus service this vehicle was being used as at the time of the crash or the primary use for the bus if not in service at the time of the crash.,Prior to 2016 the Data Element ID was V21. From 2016 to 2019 the Data Element ID was V22. This data element also appears in the Parkwork data file as PBUS_USE.,1,School,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,BUS_USE,bus_use,Bus Use,This data element describes the common type of bus service this vehicle was being used as at the time of the crash or the primary use for the bus if not in service at the time of the crash.,Prior to 2016 the Data Element ID was V21. From 2016 to 2019 the Data Element ID was V22. This data element also appears in the Parkwork data file as PBUS_USE.,4,Intercity,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,BUS_USE,bus_use,Bus Use,This data element describes the common type of bus service this vehicle was being used as at the time of the crash or the primary use for the bus if not in service at the time of the crash.,Prior to 2016 the Data Element ID was V21. From 2016 to 2019 the Data Element ID was V22. This data element also appears in the Parkwork data file as PBUS_USE.,5,Charter/Tour,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,BUS_USE,bus_use,Bus Use,This data element describes the common type of bus service this vehicle was being used as at the time of the crash or the primary use for the bus if not in service at the time of the crash.,Prior to 2016 the Data Element ID was V21. From 2016 to 2019 the Data Element ID was V22. This data element also appears in the Parkwork data file as PBUS_USE.,6,Transit/ Commuter,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,BUS_USE,bus_use,Bus Use,This data element describes the common type of bus service this vehicle was being used as at the time of the crash or the primary use for the bus if not in service at the time of the crash.,Prior to 2016 the Data Element ID was V21. From 2016 to 2019 the Data Element ID was V22. This data element also appears in the Parkwork data file as PBUS_USE.,7,Shuttle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,BUS_USE,bus_use,Bus Use,This data element describes the common type of bus service this vehicle was being used as at the time of the crash or the primary use for the bus if not in service at the time of the crash.,Prior to 2016 the Data Element ID was V21. From 2016 to 2019 the Data Element ID was V22. This data element also appears in the Parkwork data file as PBUS_USE.,8,Modified for Personal/Private Use,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,BUS_USE,bus_use,Bus Use,This data element describes the common type of bus service this vehicle was being used as at the time of the crash or the primary use for the bus if not in service at the time of the crash.,Prior to 2016 the Data Element ID was V21. From 2016 to 2019 the Data Element ID was V22. This data element also appears in the Parkwork data file as PBUS_USE.,98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,BUS_USE,bus_use,Bus Use,This data element describes the common type of bus service this vehicle was being used as at the time of the crash or the primary use for the bus if not in service at the time of the crash.,Prior to 2016 the Data Element ID was V21. From 2016 to 2019 the Data Element ID was V22. This data element also appears in the Parkwork data file as PBUS_USE.,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,0,No Special Use,1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,1,Taxi,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,2,Vehicle Used for School Transport,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,3,Vehicle Used as Other Bus,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,4,Military,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,5,Police,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,6,Ambulance,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,7,Fire Truck,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,8,Non-Transport Emergency Services Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,13,Incident Response,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,98,Not Reported,1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,EMER_USE,emer_use,Emergency Use,"This data element identifies whether this vehicle was engaged in emergency use. Emergency Motor Vehicle Use indicates operation of any motor vehicle that is legally authorized by a government authority to respond to emergencies with or without the use of emergency warning equipment, such as a police vehicle, fire truck, or ambulance while actually engaged in such response.",This data element is applicable only if the vehicle was being used as an emergency vehicle at the time of the crash. Prior to 2013 this data element’s name was “Emergency Use.” Prior to 2016 the Data Element ID was V23. From 2016 to 2019 the Data Element ID was V24. This data element also appears in the Person data file and in the Parkwork data file as PEM_USE.,0,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,EMER_USE,emer_use,Emergency Use,"This data element identifies whether this vehicle was engaged in emergency use. Emergency Motor Vehicle Use indicates operation of any motor vehicle that is legally authorized by a government authority to respond to emergencies with or without the use of emergency warning equipment, such as a police vehicle, fire truck, or ambulance while actually engaged in such response.",This data element is applicable only if the vehicle was being used as an emergency vehicle at the time of the crash. Prior to 2013 this data element’s name was “Emergency Use.” Prior to 2016 the Data Element ID was V23. From 2016 to 2019 the Data Element ID was V24. This data element also appears in the Person data file and in the Parkwork data file as PEM_USE.,2,"Non-Emergency, Non-Transport",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,EMER_USE,emer_use,Emergency Use,"This data element identifies whether this vehicle was engaged in emergency use. Emergency Motor Vehicle Use indicates operation of any motor vehicle that is legally authorized by a government authority to respond to emergencies with or without the use of emergency warning equipment, such as a police vehicle, fire truck, or ambulance while actually engaged in such response.",This data element is applicable only if the vehicle was being used as an emergency vehicle at the time of the crash. Prior to 2013 this data element’s name was “Emergency Use.” Prior to 2016 the Data Element ID was V23. From 2016 to 2019 the Data Element ID was V24. This data element also appears in the Person data file and in the Parkwork data file as PEM_USE.,3,Non-Emergency Transport,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,EMER_USE,emer_use,Emergency Use,"This data element identifies whether this vehicle was engaged in emergency use. Emergency Motor Vehicle Use indicates operation of any motor vehicle that is legally authorized by a government authority to respond to emergencies with or without the use of emergency warning equipment, such as a police vehicle, fire truck, or ambulance while actually engaged in such response.",This data element is applicable only if the vehicle was being used as an emergency vehicle at the time of the crash. Prior to 2013 this data element’s name was “Emergency Use.” Prior to 2016 the Data Element ID was V23. From 2016 to 2019 the Data Element ID was V24. This data element also appears in the Person data file and in the Parkwork data file as PEM_USE.,4,"Emergency Operation, Emergency Warning Equipment Not in Use",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,EMER_USE,emer_use,Emergency Use,"This data element identifies whether this vehicle was engaged in emergency use. Emergency Motor Vehicle Use indicates operation of any motor vehicle that is legally authorized by a government authority to respond to emergencies with or without the use of emergency warning equipment, such as a police vehicle, fire truck, or ambulance while actually engaged in such response.",This data element is applicable only if the vehicle was being used as an emergency vehicle at the time of the crash. Prior to 2013 this data element’s name was “Emergency Use.” Prior to 2016 the Data Element ID was V23. From 2016 to 2019 the Data Element ID was V24. This data element also appears in the Person data file and in the Parkwork data file as PEM_USE.,5,"Emergency Operation, Emergency Warning Equipment in Use",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,EMER_USE,emer_use,Emergency Use,"This data element identifies whether this vehicle was engaged in emergency use. Emergency Motor Vehicle Use indicates operation of any motor vehicle that is legally authorized by a government authority to respond to emergencies with or without the use of emergency warning equipment, such as a police vehicle, fire truck, or ambulance while actually engaged in such response.",This data element is applicable only if the vehicle was being used as an emergency vehicle at the time of the crash. Prior to 2013 this data element’s name was “Emergency Use.” Prior to 2016 the Data Element ID was V23. From 2016 to 2019 the Data Element ID was V24. This data element also appears in the Person data file and in the Parkwork data file as PEM_USE.,6,"Emergency Operation, Emergency Warning Equipment in Use Unknown",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,EMER_USE,emer_use,Emergency Use,"This data element identifies whether this vehicle was engaged in emergency use. Emergency Motor Vehicle Use indicates operation of any motor vehicle that is legally authorized by a government authority to respond to emergencies with or without the use of emergency warning equipment, such as a police vehicle, fire truck, or ambulance while actually engaged in such response.",This data element is applicable only if the vehicle was being used as an emergency vehicle at the time of the crash. Prior to 2013 this data element’s name was “Emergency Use.” Prior to 2016 the Data Element ID was V23. From 2016 to 2019 the Data Element ID was V24. This data element also appears in the Person data file and in the Parkwork data file as PEM_USE.,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,EMER_USE,emer_use,Emergency Use,"This data element identifies whether this vehicle was engaged in emergency use. Emergency Motor Vehicle Use indicates operation of any motor vehicle that is legally authorized by a government authority to respond to emergencies with or without the use of emergency warning equipment, such as a police vehicle, fire truck, or ambulance while actually engaged in such response.",This data element is applicable only if the vehicle was being used as an emergency vehicle at the time of the crash. Prior to 2013 this data element’s name was “Emergency Use.” Prior to 2016 the Data Element ID was V23. From 2016 to 2019 the Data Element ID was V24. This data element also appears in the Person data file and in the Parkwork data file as PEM_USE.,9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",0,Stopped Motor Vehicle In- Transport,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",1,001 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",2,002 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",3,003 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",4,004 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",5,005 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",6,006 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",7,007 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",8,008 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",9,009 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",10,010 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",11,011 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",12,012 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",13,013 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",14,014 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",15,015 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",16,016 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",17,017 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",18,018 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",19,019 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",20,020 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",21,021 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",22,022 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",23,023 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",24,024 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",25,025 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",26,026 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",27,027 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",28,028 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",29,029 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",30,030 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",31,031 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",32,032 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",33,033 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",34,034 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",35,035 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",36,036 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",37,037 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",38,038 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",39,039 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",40,040 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",41,041 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",42,042 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",43,043 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",44,044 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",45,045 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",46,046 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",47,047 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",48,048 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",49,049 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",50,050 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",51,051 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",52,052 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",53,053 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",54,054 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",55,055 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",56,056 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",57,057 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",58,058 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",59,059 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",60,060 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",61,061 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",62,062 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",63,063 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",64,064 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",65,065 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",66,066 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",67,067 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",68,068 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",69,069 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",70,070 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",71,071 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",72,072 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",73,073 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",74,074 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",75,075 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",76,076 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",77,077 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",78,078 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",79,079 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",80,080 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",81,081 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",82,082 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",83,083 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",84,084 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",85,085 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",86,086 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",87,087 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",88,088 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",89,089 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",90,090 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",91,091 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",92,092 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",93,093 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",94,094 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",95,095 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",96,096 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",97,097 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",98,098 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",99,099 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",100,100 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",101,101 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",102,102 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",103,103 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",104,104 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",105,105 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",106,106 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",107,107 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",108,108 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",109,109 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",110,110 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",111,111 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",112,112 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",113,113 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",114,114 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",115,115 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",116,116 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",117,117 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",118,118 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",119,119 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",120,120 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",121,121 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",122,122 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",123,123 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",124,124 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",125,125 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",126,126 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",127,127 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",128,128 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",129,129 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",130,130 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",131,131 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",132,132 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",133,133 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",134,134 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",135,135 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",136,136 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",137,137 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",138,138 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",139,139 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",140,140 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",141,141 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",142,142 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",143,143 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",144,144 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",145,145 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",146,146 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",147,147 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",148,148 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",149,149 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",150,150 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",151,151 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",997,Greater than 151 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",998,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",999,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,UNDERIDE,underide,Underride/Override,This data element identifies this vehicle’s involvement in an underride or override during the crash.,"Note the striking vehicle, not the vehicle struck, determines the underride/override condition. From 1975 to 1993 both the initial and principal impacts were counted. In the event and only in the event, that the initial or principal impact point was an underride/override were the data",0,No Underride or Override Noted,1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,UNDERIDE,underide,Underride/Override,This data element identifies this vehicle’s involvement in an underride or override during the crash.,"Note the striking vehicle, not the vehicle struck, determines the underride/override condition. From 1975 to 1993 both the initial and principal impacts were counted. In the event and only in the event, that the initial or principal impact point was an underride/override were the data",1,"Underriding a Motor Vehicle In-Transport, Underride, Compartment Intrusion",1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,UNDERIDE,underide,Underride/Override,This data element identifies this vehicle’s involvement in an underride or override during the crash.,"Note the striking vehicle, not the vehicle struck, determines the underride/override condition. From 1975 to 1993 both the initial and principal impacts were counted. In the event and only in the event, that the initial or principal impact point was an underride/override were the data",2,"Underriding a Motor Vehicle In-Transport, Underride, No Compartment Intrusion",1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,UNDERIDE,underide,Underride/Override,This data element identifies this vehicle’s involvement in an underride or override during the crash.,"Note the striking vehicle, not the vehicle struck, determines the underride/override condition. From 1975 to 1993 both the initial and principal impacts were counted. In the event and only in the event, that the initial or principal impact point was an underride/override were the data",3,"Underriding a Motor Vehicle In-Transport, Underride, Compartment Intrusion Unknown",1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,UNDERIDE,underide,Underride/Override,This data element identifies this vehicle’s involvement in an underride or override during the crash.,"Note the striking vehicle, not the vehicle struck, determines the underride/override condition. From 1975 to 1993 both the initial and principal impacts were counted. In the event and only in the event, that the initial or principal impact point was an underride/override were the data",4,"Underriding a Motor Vehicle Not In-Transport, Underride, Compartment Intrusion",1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,UNDERIDE,underide,Underride/Override,This data element identifies this vehicle’s involvement in an underride or override during the crash.,"Note the striking vehicle, not the vehicle struck, determines the underride/override condition. From 1975 to 1993 both the initial and principal impacts were counted. In the event and only in the event, that the initial or principal impact point was an underride/override were the data",5,"Underriding a Motor Vehicle Not In-Transport, Underride, No Compartment Intrusion",1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,UNDERIDE,underide,Underride/Override,This data element identifies this vehicle’s involvement in an underride or override during the crash.,"Note the striking vehicle, not the vehicle struck, determines the underride/override condition. From 1975 to 1993 both the initial and principal impacts were counted. In the event and only in the event, that the initial or principal impact point was an underride/override were the data",6,"Underriding a Motor Vehicle Not In-Transport, Underride, Compartment Intrusion Unknown",1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,UNDERIDE,underide,Underride/Override,This data element identifies this vehicle’s involvement in an underride or override during the crash.,"Note the striking vehicle, not the vehicle struck, determines the underride/override condition. From 1975 to 1993 both the initial and principal impacts were counted. In the event and only in the event, that the initial or principal impact point was an underride/override were the data",7,Overriding a Motor Vehicle In-Transport,1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,UNDERIDE,underide,Underride/Override,This data element identifies this vehicle’s involvement in an underride or override during the crash.,"Note the striking vehicle, not the vehicle struck, determines the underride/override condition. From 1975 to 1993 both the initial and principal impacts were counted. In the event and only in the event, that the initial or principal impact point was an underride/override were the data",8,Overriding a Motor Vehicle Not In-Transport,1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,UNDERIDE,underide,Underride/Override,This data element identifies this vehicle’s involvement in an underride or override during the crash.,"Note the striking vehicle, not the vehicle struck, determines the underride/override condition. From 1975 to 1993 both the initial and principal impacts were counted. In the event and only in the event, that the initial or principal impact point was an underride/override were the data",9,Unknown if Underride or Override,1,1,1,1,1,1,1,NA,NA,NA
FARS,vehicle,ROLLOVER,rollover,Rollover Type,This data element identifies this vehicle’s involvement in a rollover or overturn during the crash. Rollover is defined as any vehicle rotation of 90° or more about any true longitudinal or lateral axis. Rollover can occur at any time during the crash.,Data are not available from 1975 to 1977. Prior to 2016 the Data Element ID was V26. From 2016 to 2019 the Data Element ID was V27. Starting in 2022 this data element is derived from the “Sequence of Events” data element for each vehicle with an event equal to 01. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. This data element also appears in the Person data file.,0,No Rollover,1,1,1,1,1,1,1,1,1,NA
FARS,vehicle,ROLLOVER,rollover,Rollover Type,This data element identifies this vehicle’s involvement in a rollover or overturn during the crash. Rollover is defined as any vehicle rotation of 90° or more about any true longitudinal or lateral axis. Rollover can occur at any time during the crash.,Data are not available from 1975 to 1977. Prior to 2016 the Data Element ID was V26. From 2016 to 2019 the Data Element ID was V27. Starting in 2022 this data element is derived from the “Sequence of Events” data element for each vehicle with an event equal to 01. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. This data element also appears in the Person data file.,1,"Rollover, Tripped by Object/Vehicle",1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,ROLLOVER,rollover,Rollover Type,This data element identifies this vehicle’s involvement in a rollover or overturn during the crash. Rollover is defined as any vehicle rotation of 90° or more about any true longitudinal or lateral axis. Rollover can occur at any time during the crash.,Data are not available from 1975 to 1977. Prior to 2016 the Data Element ID was V26. From 2016 to 2019 the Data Element ID was V27. Starting in 2022 this data element is derived from the “Sequence of Events” data element for each vehicle with an event equal to 01. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. This data element also appears in the Person data file.,2,"Rollover, Untripped",1,1,1,1,1,1,1,1,1,NA
FARS,vehicle,ROLLOVER,rollover,Rollover Type,This data element identifies this vehicle’s involvement in a rollover or overturn during the crash. Rollover is defined as any vehicle rotation of 90° or more about any true longitudinal or lateral axis. Rollover can occur at any time during the crash.,Data are not available from 1975 to 1977. Prior to 2016 the Data Element ID was V26. From 2016 to 2019 the Data Element ID was V27. Starting in 2022 this data element is derived from the “Sequence of Events” data element for each vehicle with an event equal to 01. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. This data element also appears in the Person data file.,9,"Rollover, Unknown Type",1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,ROLINLOC,rolinloc,Location of Rollover,This data element identifies the location of the trip point or start of this vehicle’s roll.,Prior to 2016 the Data Element ID was V27. From 2016 to 2019 the Data Element ID was V28.,0,No Rollover,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,ROLINLOC,rolinloc,Location of Rollover,This data element identifies the location of the trip point or start of this vehicle’s roll.,Prior to 2016 the Data Element ID was V27. From 2016 to 2019 the Data Element ID was V28.,1,On Roadway,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,ROLINLOC,rolinloc,Location of Rollover,This data element identifies the location of the trip point or start of this vehicle’s roll.,Prior to 2016 the Data Element ID was V27. From 2016 to 2019 the Data Element ID was V28.,2,On Shoulder,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,ROLINLOC,rolinloc,Location of Rollover,This data element identifies the location of the trip point or start of this vehicle’s roll.,Prior to 2016 the Data Element ID was V27. From 2016 to 2019 the Data Element ID was V28.,3,On Median/Separator,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,ROLINLOC,rolinloc,Location of Rollover,This data element identifies the location of the trip point or start of this vehicle’s roll.,Prior to 2016 the Data Element ID was V27. From 2016 to 2019 the Data Element ID was V28.,4,In Gore,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,ROLINLOC,rolinloc,Location of Rollover,This data element identifies the location of the trip point or start of this vehicle’s roll.,Prior to 2016 the Data Element ID was V27. From 2016 to 2019 the Data Element ID was V28.,5,On Roadside,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,ROLINLOC,rolinloc,Location of Rollover,This data element identifies the location of the trip point or start of this vehicle’s roll.,Prior to 2016 the Data Element ID was V27. From 2016 to 2019 the Data Element ID was V28.,6,Outside of Trafficway,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,ROLINLOC,rolinloc,Location of Rollover,This data element identifies the location of the trip point or start of this vehicle’s roll.,Prior to 2016 the Data Element ID was V27. From 2016 to 2019 the Data Element ID was V28.,7,In Parking Lane/Zone,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,ROLINLOC,rolinloc,Location of Rollover,This data element identifies the location of the trip point or start of this vehicle’s roll.,Prior to 2016 the Data Element ID was V27. From 2016 to 2019 the Data Element ID was V28.,9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",0,Non-Collision,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",1,1 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",2,2 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",3,3 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",4,4 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",5,5 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",6,6 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",7,7 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",8,8 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",9,9 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",10,10 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",11,11 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",12,12 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",13,Top,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",14,Undercarriage,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",18,Cargo/Vehicle Parts Set-In-Motion,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",19,Other Objects Set-In-Motion,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",55,Non-Harmful Event,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",61,Left,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",62,Left-Front Side,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",63,Left-Back Side,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",77,Not a Motor Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",81,Right,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",82,Right-Front Side,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",83,Right-Back Side,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,DEFORMED,deformed,Extent of Damage,This data element records the amount of damage sustained by this vehicle as indicated in the case material based on an operational damage scale.,The data on 8 (Not Reportable) collected in 1976 are no longer contained in the data file. The data for that year are not consistent with the documentation of the time. The data element name was “Extent of Deformation” from 1975 to 2008. The data element’s name was changed to “Extent of Damage” in 2009. Prior to 2016 the Data Element ID was V29. From 2016 to 2019 the Data Element ID was V30. This data element also appears in the Parkwork Data File as PVEH_SEV.,0,No Damage,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DEFORMED,deformed,Extent of Damage,This data element records the amount of damage sustained by this vehicle as indicated in the case material based on an operational damage scale.,The data on 8 (Not Reportable) collected in 1976 are no longer contained in the data file. The data for that year are not consistent with the documentation of the time. The data element name was “Extent of Deformation” from 1975 to 2008. The data element’s name was changed to “Extent of Damage” in 2009. Prior to 2016 the Data Element ID was V29. From 2016 to 2019 the Data Element ID was V30. This data element also appears in the Parkwork Data File as PVEH_SEV.,2,Minor Damage,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DEFORMED,deformed,Extent of Damage,This data element records the amount of damage sustained by this vehicle as indicated in the case material based on an operational damage scale.,The data on 8 (Not Reportable) collected in 1976 are no longer contained in the data file. The data for that year are not consistent with the documentation of the time. The data element name was “Extent of Deformation” from 1975 to 2008. The data element’s name was changed to “Extent of Damage” in 2009. Prior to 2016 the Data Element ID was V29. From 2016 to 2019 the Data Element ID was V30. This data element also appears in the Parkwork Data File as PVEH_SEV.,4,Functional Damage,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DEFORMED,deformed,Extent of Damage,This data element records the amount of damage sustained by this vehicle as indicated in the case material based on an operational damage scale.,The data on 8 (Not Reportable) collected in 1976 are no longer contained in the data file. The data for that year are not consistent with the documentation of the time. The data element name was “Extent of Deformation” from 1975 to 2008. The data element’s name was changed to “Extent of Damage” in 2009. Prior to 2016 the Data Element ID was V29. From 2016 to 2019 the Data Element ID was V30. This data element also appears in the Parkwork Data File as PVEH_SEV.,6,Disabling Damage,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DEFORMED,deformed,Extent of Damage,This data element records the amount of damage sustained by this vehicle as indicated in the case material based on an operational damage scale.,The data on 8 (Not Reportable) collected in 1976 are no longer contained in the data file. The data for that year are not consistent with the documentation of the time. The data element name was “Extent of Deformation” from 1975 to 2008. The data element’s name was changed to “Extent of Damage” in 2009. Prior to 2016 the Data Element ID was V29. From 2016 to 2019 the Data Element ID was V30. This data element also appears in the Parkwork Data File as PVEH_SEV.,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DEFORMED,deformed,Extent of Damage,This data element records the amount of damage sustained by this vehicle as indicated in the case material based on an operational damage scale.,The data on 8 (Not Reportable) collected in 1976 are no longer contained in the data file. The data for that year are not consistent with the documentation of the time. The data element name was “Extent of Deformation” from 1975 to 2008. The data element’s name was changed to “Extent of Damage” in 2009. Prior to 2016 the Data Element ID was V29. From 2016 to 2019 the Data Element ID was V30. This data element also appears in the Parkwork Data File as PVEH_SEV.,9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,TOWED,towed,Vehicle Removal,NA,NA,2,Towed Due to Disabling Damage,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,TOWED,towed,Vehicle Removal,NA,NA,3,Towed Not Due to Disabling Damage,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,TOWED,towed,Vehicle Removal,NA,NA,5,Not Towed,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,TOWED,towed,Vehicle Removal,NA,NA,8,Not Reported,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,TOWED,towed,Vehicle Removal,NA,NA,9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",1,Rollover/Overturn,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",2,Fire/Explosion,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",3,Immersion or Partial Immersion,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",4,Gas Inhalation,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",5,Fell/Jumped from Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",6,Injured In Vehicle (Non-Collision),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",7,Other Non-Collision,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",8,Pedestrian,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",9,Pedalcyclist,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",10,Railway Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",11,Live Animal,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",12,Motor Vehicle In-Transport,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",14,Parked Motor Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",15,Non-Motorist on Personal Conveyance,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",16,Thrown or Falling Object,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",17,Boulder,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",18,Other Object (not fixed),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",19,Building,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",20,Impact Attenuator/Crash Cushion,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",21,Bridge Pier or Support,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",23,Bridge Rail (Includes parapet),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",24,Guardrail Face,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",25,Concrete Traffic Barrier,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",26,Other Traffic Barrier,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",30,Utility Pole/Light Support,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",31,"Other Post, Other Pole or Other Supports",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",32,Culvert,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",33,Curb,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",34,Ditch,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",35,Embankment,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",38,Fence,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",39,Wall,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",40,Fire Hydrant,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",41,Shrubbery,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",42,Tree (Standing Only),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",43,Other Fixed Object,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",44,"Pavement Surface Irregularity (Ruts, Potholes, Grates, etc.)",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",45,Working Motor Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",46,Traffic Signal Support,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",48,Snow Bank,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",49,Ridden Animal or Animal Drawn Conveyance,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",50,Bridge Overhead Structure,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",51,Jackknife (harmful to this vehicle),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",52,Guardrail End,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",53,Mail Box,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",54,"Motor Vehicle In-Transport Strikes or is Struck by Cargo, Persons or Objects Set-in-Motion from/by Another Motor Vehicle In Transport",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",55,Motor Vehicle in Motion Outside the Trafficway,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",57,Cable Barrier,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",58,Ground,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",59,Traffic Sign Support,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",72,Cargo/Equipment Loss or Shift (harmful to this vehicle),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",73,Object Fell From Motor Vehicle In-Transport,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",30,Multi-Wheeled Motorcycle Conversion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",32,Vehicle Registration for Handicapped,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",33,Vehicle Being Pushed by Non-Motorist,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",35,Reconstructed/Altered Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",37,Transporting Children To/From Head Start/Day Care,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",39,"Highway Construction, Maintenance, or Utility Vehicle, In Transport (Inside or Outside Workzone)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",40,Highway Incident Response Vehicle,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",41,"Police, Fire, or EMS Vehicle Working at the Scene of an Emergency or Performing Other Traffic Control Activities",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",42,"Other Working Vehicle (Not Construction, Maintenance, Utility, Police, Fire, or EMS Vehicle)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",44,Adaptive Equipment,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",30,Multi-Wheeled Motorcycle Conversion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",32,Vehicle Registration for Handicapped,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",33,Vehicle Being Pushed by Non-Motorist,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",35,Reconstructed/Altered Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",37,Transporting Children To/From Head Start/Day Care,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",39,"Highway Construction, Maintenance, or Utility Vehicle, In Transport (Inside or Outside Workzone)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",40,Highway Incident Response Vehicle,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",41,"Police, Fire, or EMS Vehicle Working at the Scene of an Emergency or Performing Other Traffic Control Activities",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",42,"Other Working Vehicle (Not Construction, Maintenance, Utility, Police, Fire, or EMS Vehicle)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",44,Adaptive Equipment,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,FIRE_EXP,fire_exp,Fire Occurrence,This data element identifies whether a fire in any way related to the crash occurred in this vehicle.,"From 1975 to 1979, if an explosion occurred in the vehicle with or without a fire, this data element would also be set to 1. From 2017 to 2018 the Data Element ID was V35. From 2016 to 2019 the Data Element ID was V34. This data element also appears in the Person data file and in the Parkwork data file as PFIRE.",0,No or Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,FIRE_EXP,fire_exp,Fire Occurrence,This data element identifies whether a fire in any way related to the crash occurred in this vehicle.,"From 1975 to 1979, if an explosion occurred in the vehicle with or without a fire, this data element would also be set to 1. From 2017 to 2018 the Data Element ID was V35. From 2016 to 2019 the Data Element ID was V34. This data element also appears in the Person data file and in the Parkwork data file as PFIRE.",1,Yes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_PRES,dr_pres,Driver Presence,This data element identifies whether a driver was present in this vehicle at the onset of the unstabilized situation.,NA,0,No Driver Present/Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_PRES,dr_pres,Driver Presence,This data element identifies whether a driver was present in this vehicle at the onset of the unstabilized situation.,NA,1,Yes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_PRES,dr_pres,Driver Presence,This data element identifies whether a driver was present in this vehicle at the onset of the unstabilized situation.,NA,9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,0,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,3,American Samoa,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,6,California,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,14,Guam,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,36,New York,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,93,Indian Nation,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,94,U.S. Government,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,95,Canada,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,96,Mexico,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,97,Other Foreign Country,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_ZIP,dr_zip,Driver ZIP Code,This data element records the ZIP Code of the driver’s address as listed in the case material.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",0,Not resident of U.S. or Territories,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_ZIP,dr_zip,Driver ZIP Code,This data element records the ZIP Code of the driver’s address as listed in the case material.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",99997,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_ZIP,dr_zip,Driver ZIP Code,This data element records the ZIP Code of the driver’s address as listed in the case material.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",99999,Unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,L_STATUS,l_status,Non-CDL License Status,This data element identifies the status of the driver’s license at the time of the crash.,"For 1975-1981, values 3 and 7 make up the valid license category. For 1982-1986, values 2, 7, and 8 are all valid license categories. For 1987-1992, values 5, 6, 7, and 8 make up the valid license category. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",0,Not licensed,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATUS,l_status,Non-CDL License Status,This data element identifies the status of the driver’s license at the time of the crash.,"For 1975-1981, values 3 and 7 make up the valid license category. For 1982-1986, values 2, 7, and 8 are all valid license categories. For 1987-1992, values 5, 6, 7, and 8 make up the valid license category. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",1,Suspended,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATUS,l_status,Non-CDL License Status,This data element identifies the status of the driver’s license at the time of the crash.,"For 1975-1981, values 3 and 7 make up the valid license category. For 1982-1986, values 2, 7, and 8 are all valid license categories. For 1987-1992, values 5, 6, 7, and 8 make up the valid license category. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",2,Revoked,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATUS,l_status,Non-CDL License Status,This data element identifies the status of the driver’s license at the time of the crash.,"For 1975-1981, values 3 and 7 make up the valid license category. For 1982-1986, values 2, 7, and 8 are all valid license categories. For 1987-1992, values 5, 6, 7, and 8 make up the valid license category. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",3,Expired,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATUS,l_status,Non-CDL License Status,This data element identifies the status of the driver’s license at the time of the crash.,"For 1975-1981, values 3 and 7 make up the valid license category. For 1982-1986, values 2, 7, and 8 are all valid license categories. For 1987-1992, values 5, 6, 7, and 8 make up the valid license category. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",4,Canceled or denied,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATUS,l_status,Non-CDL License Status,This data element identifies the status of the driver’s license at the time of the crash.,"For 1975-1981, values 3 and 7 make up the valid license category. For 1982-1986, values 2, 7, and 8 are all valid license categories. For 1987-1992, values 5, 6, 7, and 8 make up the valid license category. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",6,Valid,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATUS,l_status,Non-CDL License Status,This data element identifies the status of the driver’s license at the time of the crash.,"For 1975-1981, values 3 and 7 make up the valid license category. For 1982-1986, values 2, 7, and 8 are all valid license categories. For 1987-1992, values 5, 6, 7, and 8 make up the valid license category. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",7,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_STATUS,l_status,Non-CDL License Status,This data element identifies the status of the driver’s license at the time of the crash.,"For 1975-1981, values 3 and 7 make up the valid license category. For 1982-1986, values 2, 7, and 8 are all valid license categories. For 1987-1992, values 5, 6, 7, and 8 make up the valid license category. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",9,Unknown License Status,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_TYPE,l_type,Non-CDL License Type,This data element identifies the type of license held by this driver at the time of the crash.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",0,Not Licensed,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_TYPE,l_type,Non-CDL License Type,This data element identifies the type of license held by this driver at the time of the crash.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",1,Full Driver License,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_TYPE,l_type,Non-CDL License Type,This data element identifies the type of license held by this driver at the time of the crash.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",2,Intermediate Driver License,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_TYPE,l_type,Non-CDL License Type,This data element identifies the type of license held by this driver at the time of the crash.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",6,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_TYPE,l_type,Non-CDL License Type,This data element identifies the type of license held by this driver at the time of the crash.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",7,Learner`s Permit,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_TYPE,l_type,Non-CDL License Type,This data element identifies the type of license held by this driver at the time of the crash.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",8,Temporary License,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_TYPE,l_type,Non-CDL License Type,This data element identifies the type of license held by this driver at the time of the crash.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). NA",9,Unknown License Type,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CDL_STAT,cdl_stat,Commercial MV License Status,This data element indicates the status of the driver’s commercial driver’s license (CDL) if applicable.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",0,No (CDL),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CDL_STAT,cdl_stat,Commercial MV License Status,This data element indicates the status of the driver’s commercial driver’s license (CDL) if applicable.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",1,Suspended,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CDL_STAT,cdl_stat,Commercial MV License Status,This data element indicates the status of the driver’s commercial driver’s license (CDL) if applicable.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",2,Revoked,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CDL_STAT,cdl_stat,Commercial MV License Status,This data element indicates the status of the driver’s commercial driver’s license (CDL) if applicable.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",3,Expired,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CDL_STAT,cdl_stat,Commercial MV License Status,This data element indicates the status of the driver’s commercial driver’s license (CDL) if applicable.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",4,Cancelled or Denied,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CDL_STAT,cdl_stat,Commercial MV License Status,This data element indicates the status of the driver’s commercial driver’s license (CDL) if applicable.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",5,Disqualified,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CDL_STAT,cdl_stat,Commercial MV License Status,This data element indicates the status of the driver’s commercial driver’s license (CDL) if applicable.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",6,Valid,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CDL_STAT,cdl_stat,Commercial MV License Status,This data element indicates the status of the driver’s commercial driver’s license (CDL) if applicable.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",7,Learner`s Permit,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,CDL_STAT,cdl_stat,Commercial MV License Status,This data element indicates the status of the driver’s commercial driver’s license (CDL) if applicable.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",8,Other Not-Valid,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CDL_STAT,cdl_stat,Commercial MV License Status,This data element indicates the status of the driver’s commercial driver’s license (CDL) if applicable.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",97,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,CDL_STAT,cdl_stat,Commercial MV License Status,This data element indicates the status of the driver’s commercial driver’s license (CDL) if applicable.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",99,Unknown License Status,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_ENDORS,l_endors,Compliance with CDL Endorsements,This data element identifies whether the vehicle driven at the time of the crash required endorsements on a commercial driver’s license (CDL) and whether this driver was complying with the CDL endorsements.,"Data was not collected prior to 1991. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",0,No Endorsements required for this vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_ENDORS,l_endors,Compliance with CDL Endorsements,This data element identifies whether the vehicle driven at the time of the crash required endorsements on a commercial driver’s license (CDL) and whether this driver was complying with the CDL endorsements.,"Data was not collected prior to 1991. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",1,"Endorsement(s) Required, Complied with",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_ENDORS,l_endors,Compliance with CDL Endorsements,This data element identifies whether the vehicle driven at the time of the crash required endorsements on a commercial driver’s license (CDL) and whether this driver was complying with the CDL endorsements.,"Data was not collected prior to 1991. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",2,"Endorsement(s) Required, Not Complied with",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_ENDORS,l_endors,Compliance with CDL Endorsements,This data element identifies whether the vehicle driven at the time of the crash required endorsements on a commercial driver’s license (CDL) and whether this driver was complying with the CDL endorsements.,"Data was not collected prior to 1991. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",3,"Endorsement(s) Required, Compliance Unknown",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_ENDORS,l_endors,Compliance with CDL Endorsements,This data element identifies whether the vehicle driven at the time of the crash required endorsements on a commercial driver’s license (CDL) and whether this driver was complying with the CDL endorsements.,"Data was not collected prior to 1991. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",7,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_ENDORS,l_endors,Compliance with CDL Endorsements,This data element identifies whether the vehicle driven at the time of the crash required endorsements on a commercial driver’s license (CDL) and whether this driver was complying with the CDL endorsements.,"Data was not collected prior to 1991. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",9,"Unknown, if required",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_COMPL,l_compl,License Compliance with Class of Vehicle,NA,NA,0,Not licensed,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_COMPL,l_compl,License Compliance with Class of Vehicle,NA,NA,1,No license required for this class vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_COMPL,l_compl,License Compliance with Class of Vehicle,NA,NA,2,No valid license for this class vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_COMPL,l_compl,License Compliance with Class of Vehicle,NA,NA,3,Valid license for this class vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_COMPL,l_compl,License Compliance with Class of Vehicle,NA,NA,6,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_COMPL,l_compl,License Compliance with Class of Vehicle,NA,NA,8,Unknown If CDL and/or CDL endorsement required for this vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_COMPL,l_compl,License Compliance with Class of Vehicle,NA,NA,9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_RESTRI,l_restri,Compliance with License Restrictions,This data element indicates whether this driver was compliant with restrictions on their license.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",0,No Restrictions or Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_RESTRI,l_restri,Compliance with License Restrictions,This data element indicates whether this driver was compliant with restrictions on their license.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",1,Restrictions Complied With,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_RESTRI,l_restri,Compliance with License Restrictions,This data element indicates whether this driver was compliant with restrictions on their license.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",2,Restrictions Not Complied With,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_RESTRI,l_restri,Compliance with License Restrictions,This data element indicates whether this driver was compliant with restrictions on their license.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",3,"Restrictions, Compliance Unknown",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_RESTRI,l_restri,Compliance with License Restrictions,This data element indicates whether this driver was compliant with restrictions on their license.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",7,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,L_RESTRI,l_restri,Compliance with License Restrictions,This data element indicates whether this driver was compliant with restrictions on their license.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_HGT,dr_hgt,Driver Height,This data element identifies this driver’s height (in inches).,"This information was coded in two subfields that are in feet or in inches. If both the Driver Height in feet and Driver Height in inches are known, then we do the conversion using (Feet)*12 + inches; if feet are unknown or if inches are 98 (Other) or 99 (Unknown) then DR_HGT=999 (Unknown). Minimum height 2 feet = 24 inches, maximum height 8 feet 11 inches = 107 inches. In 2009, if feet and/or inches are unknown (9,99) or blank, then the Driver Height is left blank. However, in 2010 if feet and/or inches are unknown (9,99) then the Driver Height is computed as 999 (Unknown). The Driver Presence data element is not taken into account. In 2011, if feet and/or inches are unknown (9,99) and Driver Presence is 1, then the Driver Height is computed as 999 (Unknown) otherwise Driver Height is computed as 998 (No Driver Present/Unknown if Driver Present).",NA,(Self-evident),1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",40,40 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",41,41 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",42,42 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",43,43 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",44,44 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",45,45 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",46,46 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",47,47 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",48,48 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",49,49 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",50,50 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",51,51 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",52,52 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",53,53 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",54,54 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",55,55 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",56,56 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",57,57 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",58,58 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",59,59 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",60,60 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",61,61 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",62,62 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",63,63 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",64,64 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",65,65 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",66,66 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",67,67 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",68,68 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",69,69 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",70,70 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",71,71 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",72,72 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",73,73 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",74,74 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",75,75 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",76,76 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",77,77 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",78,78 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",79,79 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",80,80 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",81,81 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",82,82 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",83,83 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",84,84 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",85,85 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",86,86 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",87,87 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",88,88 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",89,89 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",90,90 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",91,91 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",92,92 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",93,93 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",94,94 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",95,95 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",96,96 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",97,97 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",98,98 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",99,99 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",100,100 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",101,101 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",102,102 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",103,103 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",104,104 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",105,105 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",106,106 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",107,107 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",108,108 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",109,109 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",110,110 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",111,111 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",112,112 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",113,113 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",114,114 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",115,115 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",116,116 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",117,117 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",118,118 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",119,119 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",120,120 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",121,121 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",122,122 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",123,123 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",124,124 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",125,125 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",126,126 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",127,127 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",128,128 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",129,129 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",130,130 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",131,131 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",132,132 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",133,133 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",134,134 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",135,135 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",136,136 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",137,137 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",138,138 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",139,139 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",140,140 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",141,141 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",142,142 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",143,143 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",144,144 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",145,145 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",146,146 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",147,147 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",148,148 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",149,149 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",150,150 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",151,151 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",152,152 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",153,153 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",154,154 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",155,155 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",156,156 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",157,157 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",158,158 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",159,159 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",160,160 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",161,161 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",162,162 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",163,163 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",164,164 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",165,165 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",166,166 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",167,167 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",168,168 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",169,169 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",170,170 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",171,171 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",172,172 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",173,173 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",174,174 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",175,175 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",176,176 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",177,177 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",178,178 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",179,179 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",180,180 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",181,181 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",182,182 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",183,183 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",184,184 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",185,185 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",186,186 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",187,187 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",188,188 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",189,189 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",190,190 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",191,191 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",192,192 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",193,193 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",194,194 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",195,195 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",196,196 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",197,197 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",198,198 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",199,199 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",200,200 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",201,201 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",202,202 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",203,203 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",204,204 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",205,205 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",206,206 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",207,207 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",208,208 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",209,209 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",210,210 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",211,211 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",212,212 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",213,213 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",214,214 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",215,215 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",216,216 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",217,217 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",218,218 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",219,219 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",220,220 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",221,221 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",222,222 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",223,223 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",224,224 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",225,225 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",226,226 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",227,227 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",228,228 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",229,229 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",230,230 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",231,231 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",232,232 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",233,233 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",234,234 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",235,235 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",236,236 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",237,237 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",238,238 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",239,239 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",240,240 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",241,241 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",242,242 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",243,243 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",244,244 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",245,245 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",246,246 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",247,247 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",248,248 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",249,249 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",250,250 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",251,251 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",252,252 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",253,253 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",254,254 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",255,255 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",256,256 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",257,257 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",258,258 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",259,259 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",260,260 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",261,261 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",262,262 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",263,263 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",264,264 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",265,265 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",266,266 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",267,267 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",268,268 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",269,269 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",270,270 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",271,271 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",272,272 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",273,273 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",274,274 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",275,275 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",276,276 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",277,277 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",278,278 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",279,279 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",280,280 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",281,281 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",282,282 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",283,283 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",284,284 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",285,285 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",286,286 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",287,287 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",288,288 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",289,289 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",290,290 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",291,291 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",292,292 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",293,293 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",294,294 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",295,295 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",296,296 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",297,297 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",298,298 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",299,299 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",300,300 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",301,301 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",302,302 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",303,303 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",304,304 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",305,305 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",306,306 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",307,307 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",308,308 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",309,309 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",310,310 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",311,311 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",312,312 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",313,313 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",314,314 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",315,315 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",316,316 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",317,317 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",318,318 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",319,319 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",320,320 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",321,321 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",322,322 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",323,323 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",324,324 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",325,325 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",326,326 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",327,327 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",328,328 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",329,329 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",330,330 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",331,331 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",332,332 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",333,333 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",334,334 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",335,335 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",336,336 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",337,337 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",338,338 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",339,339 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",340,340 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",341,341 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",342,342 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",343,343 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",344,344 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",345,345 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",346,346 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",347,347 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",348,348 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",349,349 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",350,350 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",351,351 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",352,352 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",353,353 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",354,354 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",355,355 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",356,356 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",357,357 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",358,358 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",359,359 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",360,360 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",361,361 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",362,362 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",363,363 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",364,364 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",365,365 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",366,366 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",367,367 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",368,368 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",369,369 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",370,370 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",371,371 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",372,372 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",373,373 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",374,374 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",375,375 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",376,376 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",377,377 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",378,378 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",379,379 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",380,380 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",381,381 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",382,382 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",383,383 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",384,384 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",385,385 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",386,386 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",387,387 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",388,388 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",389,389 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",390,390 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",391,391 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",392,392 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",393,393 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",394,394 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",395,395 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",396,396 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",397,397 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",398,398 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",399,399 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",400,400 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",401,401 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",402,402 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",403,403 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",404,404 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",405,405 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",406,406 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",407,407 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",408,408 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",409,409 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",410,410 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",411,411 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",412,412 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",413,413 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",414,414 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",415,415 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",416,416 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",417,417 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",418,418 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",419,419 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",420,420 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",421,421 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",422,422 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",423,423 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",424,424 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",425,425 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",426,426 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",427,427 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",428,428 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",429,429 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",430,430 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",431,431 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",432,432 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",433,433 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",434,434 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",435,435 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",436,436 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",437,437 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",438,438 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",439,439 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",440,440 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",441,441 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",442,442 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",443,443 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",444,444 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",445,445 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",446,446 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",447,447 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",448,448 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",449,449 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",450,450 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",451,451 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",452,452 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",453,453 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",454,454 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",455,455 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",456,456 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",457,457 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",458,458 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",459,459 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",460,460 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",461,461 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",462,462 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",463,463 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",464,464 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",465,465 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",466,466 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",467,467 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",468,468 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",469,469 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",470,470 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",471,471 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",472,472 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",473,473 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",474,474 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",475,475 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",476,476 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",477,477 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",478,478 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",479,479 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",480,480 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",481,481 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",482,482 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",483,483 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",484,484 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",485,485 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",486,486 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",487,487 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",488,488 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",489,489 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",490,490 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",491,491 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",492,492 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",493,493 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",494,494 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",495,495 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",496,496 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",497,497 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",498,498 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",499,499 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",500,500 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",501,501 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",502,502 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",503,503 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",504,504 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",505,505 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",506,506 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",507,507 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",508,508 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",509,509 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",510,510 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",511,511 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",512,512 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",513,513 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",514,514 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",515,515 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",516,516 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",517,517 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",518,518 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",519,519 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",520,520 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",521,521 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",522,522 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",523,523 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",524,524 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",525,525 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",526,526 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",527,527 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",528,528 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",529,529 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",530,530 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",531,531 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",532,532 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",533,533 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",534,534 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",535,535 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",536,536 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",537,537 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",538,538 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",539,539 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",540,540 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",541,541 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",542,542 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",543,543 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",544,544 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",545,545 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",546,546 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",547,547 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",548,548 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",549,549 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",550,550 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",551,551 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",552,552 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",553,553 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",554,554 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",555,555 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",556,556 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",557,557 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",558,558 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",559,559 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",560,560 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",561,561 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",562,562 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",563,563 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",564,564 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",565,565 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",566,566 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",567,567 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",568,568 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",569,569 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",570,570 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",571,571 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",572,572 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",573,573 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",574,574 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",575,575 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",576,576 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",577,577 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",578,578 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",579,579 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",580,580 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",581,581 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",582,582 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",583,583 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",584,584 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",585,585 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",586,586 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",587,587 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",588,588 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",589,589 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",590,590 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",591,591 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",592,592 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",593,593 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",594,594 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",595,595 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",596,596 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",597,597 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",598,598 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",599,599 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",600,600 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",601,601 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",602,602 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",603,603 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",604,604 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",605,605 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",606,606 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",607,607 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",608,608 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",609,609 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",610,610 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",611,611 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",612,612 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",613,613 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",614,614 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",615,615 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",616,616 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",617,617 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",618,618 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",619,619 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",620,620 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",621,621 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",622,622 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",623,623 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",624,624 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",625,625 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",626,626 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",627,627 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",628,628 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",629,629 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",630,630 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",631,631 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",632,632 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",633,633 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",634,634 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",635,635 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",636,636 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",637,637 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",638,638 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",639,639 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",640,640 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",641,641 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",642,642 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",643,643 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",644,644 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",645,645 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",646,646 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",647,647 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",648,648 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",649,649 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",650,650 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",651,651 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",652,652 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",653,653 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",654,654 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",655,655 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",656,656 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",657,657 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",658,658 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",659,659 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",660,660 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",661,661 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",662,662 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",663,663 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",664,664 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",665,665 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",666,666 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",667,667 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",668,668 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",669,669 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",670,670 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",671,671 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",672,672 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",673,673 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",674,674 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",675,675 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",676,676 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",677,677 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",678,678 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",679,679 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",680,680 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",681,681 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",682,682 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",683,683 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",684,684 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",685,685 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",686,686 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",687,687 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",688,688 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",689,689 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",690,690 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",691,691 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",692,692 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",693,693 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",694,694 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",695,695 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",696,696 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",697,697 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",698,698 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",699,699 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",700,700 lbs.,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",997,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",998,Other,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_WGT,dr_wgt,Driver Weight,This data element identifies this driver’s weight (in pounds).,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",999,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",0,None,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",1,1,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",2,2,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",3,3,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",4,4,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",5,5,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",6,6,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",7,7,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",8,8,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",9,9,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",10,10,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",11,11,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",12,12,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",13,13,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",14,14,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",15,15,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",16,16,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",17,17,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",18,18,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",19,19,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",20,20,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",21,21,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",22,22,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",23,23,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",24,24,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",25,25,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",26,26,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",27,27,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",28,28,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",29,29,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",30,30,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",31,31,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",32,32,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",33,33,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",34,34,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",35,35,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",36,36,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",37,37,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",38,38,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",39,39,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",40,40,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",41,41,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",42,42,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",43,43,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",44,44,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",45,45,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",46,46,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",47,47,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",48,48,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",49,49,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",50,50,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",51,51,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",52,52,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",53,53,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",54,54,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",55,55,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",56,56,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",57,57,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",58,58,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",59,59,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",60,60,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",61,61,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",62,62,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",63,63,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",64,64,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",65,65,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",66,66,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",67,67,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",68,68,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",69,69,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",70,70,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",71,71,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",72,72,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",73,73,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",74,74,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",75,75,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",76,76,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",77,77,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",78,78,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",79,79,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",80,80,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",81,81,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",82,82,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",83,83,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",84,84,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",85,85,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",86,86,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",87,87,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",88,88,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",89,89,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",90,90,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",91,91,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",92,92,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",93,93,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",94,94,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",95,95,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",96,96,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",97,97,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",98,Crashes Not Reported on Driving Record,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_ACC,prev_acc,Previous Recorded Crashes,This data element records any previous crashes for this driver that occurred within 5 years of the crash date.,"Prior to 2011 if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",998,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",0,None,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",1,1,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",2,2,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",3,3,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",4,4,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",5,5,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",6,6,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",7,7,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",8,8,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",9,9,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",10,10,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",11,11,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",12,12,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",13,13,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",14,14,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",15,15,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",16,16,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",17,17,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",18,18,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",19,19,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",20,20,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",21,21,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",22,22,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",23,23,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",24,24,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",25,25,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",26,26,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",27,27,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",28,28,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",29,29,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",30,30,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",31,31,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",32,32,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",33,33,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",34,34,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",35,35,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",36,36,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",37,37,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",38,38,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",39,39,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",40,40,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",41,41,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",42,42,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",43,43,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",44,44,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",45,45,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",46,46,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",47,47,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",48,48,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",49,49,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",50,50,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",51,51,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",52,52,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",53,53,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",54,54,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",55,55,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",56,56,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",57,57,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",58,58,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",59,59,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",60,60,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",61,61,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",62,62,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",63,63,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",64,64,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",65,65,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",66,66,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",67,67,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",68,68,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",69,69,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",70,70,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",71,71,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",72,72,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",73,73,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",74,74,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",75,75,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",76,76,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",77,77,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",78,78,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",79,79,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",80,80,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",81,81,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",82,82,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",83,83,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",84,84,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",85,85,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",86,86,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",87,87,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",88,88,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",89,89,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",90,90,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",91,91,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",92,92,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",93,93,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",94,94,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",95,95,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",96,96,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",97,97,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_SUS,prev_sus,Previous Recorded Suspensions and Revocations,This data element records any previous license suspensions or revocations for this driver that occurred within 5* years of the crash date.,"If a driver has been disqualified for a CDL, this event is recorded in Previous Recorded Suspensions and Revocations. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). * Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",998,No Driver Present/Unknown if Driver Present,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",0,None,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",1,1,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",2,2,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",3,3,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",4,4,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",5,5,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",6,6,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",7,7,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",8,8,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",9,9,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",10,10,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",11,11,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",12,12,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",13,13,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",14,14,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",15,15,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",16,16,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",17,17,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",18,18,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",19,19,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",20,20,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",21,21,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",22,22,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",23,23,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",24,24,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",25,25,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",26,26,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",27,27,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",28,28,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",29,29,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",30,30,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",31,31,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",32,32,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",33,33,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",34,34,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",35,35,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",36,36,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",37,37,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",38,38,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",39,39,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",40,40,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",41,41,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",42,42,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",43,43,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",44,44,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",45,45,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",46,46,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",47,47,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",48,48,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",49,49,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",50,50,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",51,51,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",52,52,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",53,53,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",54,54,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",55,55,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",56,56,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",57,57,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",58,58,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",59,59,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",60,60,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",61,61,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",62,62,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",63,63,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",64,64,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",65,65,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",66,66,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",67,67,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",68,68,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",69,69,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",70,70,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",71,71,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",72,72,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",73,73,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",74,74,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",75,75,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",76,76,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",77,77,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",78,78,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",79,79,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",80,80,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",81,81,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",82,82,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",83,83,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",84,84,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",85,85,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",86,86,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",87,87,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",88,88,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",89,89,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",90,90,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",91,91,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",92,92,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",93,93,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",94,94,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",95,95,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",96,96,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",97,97,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_DWI,prev_dwi,Previous DWI Convictions,This data element records any previous DWI convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",998,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",0,None,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",1,1,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",2,2,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",3,3,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",4,4,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",5,5,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",6,6,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",7,7,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",8,8,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",9,9,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",10,10,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",11,11,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",12,12,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",13,13,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",14,14,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",15,15,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",16,16,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",17,17,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",18,18,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",19,19,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",20,20,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",21,21,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",22,22,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",23,23,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",24,24,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",25,25,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",26,26,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",27,27,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",28,28,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",29,29,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",30,30,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",31,31,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",32,32,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",33,33,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",34,34,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",35,35,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",36,36,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",37,37,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",38,38,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",39,39,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",40,40,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",41,41,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",42,42,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",43,43,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",44,44,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",45,45,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",46,46,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",47,47,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",48,48,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",49,49,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",50,50,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",51,51,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",52,52,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",53,53,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",54,54,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",55,55,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",56,56,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",57,57,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",58,58,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",59,59,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",60,60,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",61,61,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",62,62,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",63,63,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",64,64,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",65,65,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",66,66,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",67,67,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",68,68,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",69,69,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",70,70,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",71,71,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",72,72,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",73,73,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",74,74,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",75,75,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",76,76,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",77,77,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",78,78,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",79,79,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",80,80,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",81,81,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",82,82,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",83,83,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",84,84,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",85,85,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",86,86,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",87,87,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",88,88,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",89,89,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",90,90,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",91,91,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",92,92,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",93,93,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",94,94,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",95,95,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",96,96,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",97,97,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_SPD,prev_spd,Previous Speeding Convictions,This data element records any previous speeding convictions for this driver that occurred within 5 years of the crash date.,"Speeding violations count going too slow as well as going too fast. Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",998,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",0,None,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",1,1,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",2,2,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",3,3,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",4,4,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",5,5,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",6,6,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",7,7,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",8,8,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",9,9,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",10,10,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",11,11,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",12,12,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",13,13,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",14,14,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",15,15,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",16,16,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",17,17,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",18,18,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",19,19,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",20,20,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",21,21,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",22,22,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",23,23,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",24,24,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",25,25,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",26,26,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",27,27,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",28,28,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",29,29,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",30,30,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",31,31,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",32,32,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",33,33,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",34,34,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",35,35,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",36,36,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",37,37,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",38,38,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",39,39,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",40,40,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",41,41,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",42,42,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",43,43,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",44,44,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",45,45,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",46,46,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",47,47,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",48,48,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",49,49,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",50,50,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",51,51,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",52,52,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",53,53,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",54,54,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",55,55,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",56,56,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",57,57,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",58,58,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",59,59,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",60,60,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",61,61,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",62,62,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",63,63,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",64,64,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",65,65,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",66,66,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",67,67,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",68,68,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",69,69,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",70,70,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",71,71,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",72,72,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",73,73,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",74,74,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",75,75,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",76,76,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",77,77,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",78,78,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",79,79,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",80,80,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",81,81,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",82,82,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",83,83,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",84,84,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",85,85,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",86,86,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",87,87,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",88,88,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",89,89,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",90,90,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",91,91,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",92,92,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",93,93,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",94,94,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",95,95,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",96,96,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",97,97,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",99,Unknown,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Harmful MV Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",998,No Driver Present/Unknown if Driver Present,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",0,No Record,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",1,January,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",2,February,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",3,March,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",4,April,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",5,May,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",6,June,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",7,July,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",8,August,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",9,September,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",10,October,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",11,November,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",12,December,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",98,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_MO,first_mo,"Date of First Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",99,Unknown,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",0,No Record,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2005,2005,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2006,2006,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2009,2009,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2010,2010,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2011,2011,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2012,2012,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2013,2013,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2014,2014,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",9998,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",9999,Unknown,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",0,No Record,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",1,January,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",2,February,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",3,March,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",4,April,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",5,May,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",6,June,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",7,July,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",8,August,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",9,September,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",10,October,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",11,November,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",12,December,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",98,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_MO,last_mo,"Date of Last Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",99,Unknown,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",0,No Record,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2005,2005,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2006,2006,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2009,2009,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2010,2010,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2011,2011,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2012,2012,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2013,2013,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2014,2014,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",9998,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",9999,Unknown,1,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,SPEEDREL,speedrel,Speeding Related,"This data element identifies if the driver was speeding, and it was related to the crash as identified by law enforcement.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2013 this data element’s name was “Speed-Related.”",0,No,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEEDREL,speedrel,Speeding Related,"This data element identifies if the driver was speeding, and it was related to the crash as identified by law enforcement.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2013 this data element’s name was “Speed-Related.”",2,"Yes, Racing",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEEDREL,speedrel,Speeding Related,"This data element identifies if the driver was speeding, and it was related to the crash as identified by law enforcement.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2013 this data element’s name was “Speed-Related.”",3,"Yes, Exceeded Speed Limit",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEEDREL,speedrel,Speeding Related,"This data element identifies if the driver was speeding, and it was related to the crash as identified by law enforcement.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2013 this data element’s name was “Speed-Related.”",4,"Yes, Too Fast for Conditions",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEEDREL,speedrel,Speeding Related,"This data element identifies if the driver was speeding, and it was related to the crash as identified by law enforcement.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2013 this data element’s name was “Speed-Related.”",5,"Yes, Specifics Unknown",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEEDREL,speedrel,Speeding Related,"This data element identifies if the driver was speeding, and it was related to the crash as identified by law enforcement.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2013 this data element’s name was “Speed-Related.”",8,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,SPEEDREL,speedrel,Speeding Related,"This data element identifies if the driver was speeding, and it was related to the crash as identified by law enforcement.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2013 this data element’s name was “Speed-Related.”",9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,4,Reaction to or Failure to Take Drugs/Medication,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,6,Careless Driving,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,8,Aggressive Driving / Road Rage,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,12,Mother of Dead Fetus/ Mother of Infant Born Post Crash,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,13,Mentally Challenged,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,15,"Seat Back Not In Normal Upright Position, Seat Back Reclined",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,16,Police or Law Enforcement Officer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,18,Traveling on Prohibited Trafficways,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,19,Legally Driving on Suspended or Revoked License,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,20,Leaving Vehicle Unattended with Engine Running. Leaving Vehicle Unattended in Roadway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,21,Overloading or Improper Loading of Vehicle with Passengers or Cargo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,22,Towing or Pushing Vehicle Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,23,Failing to Dim Lights or to Have Lights on When Required,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,24,Operating without Required Equipment,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,26,Following Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,27,Improper or Erratic Lane Changing,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,28,Failure to keep in Proper Lane,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,29,"Intentional Illegal Driving on Road Shoulder, in Ditch, on Sidewalk or on Median",1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,30,Making Improper Entry to or Exit from Trafficway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,31,Starting or Backing Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,32,Opening Closure into Moving Traffic or While Vehicle is in Motion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,33,"Passing where Prohibited by Posted Signs, Pavement Markings, Hill or Curve, or School Bus Displaying Warning not to Pass",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,34,Passing on Wrong Side,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,35,Passing with Insufficient Distance or Inadequate Visibility or Failing to Yield to Overtaking Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,36,"Operating the Vehicle in an Erratic, Reckless or Negligent Manner, Operating at Erratic or Suddenly Changing Speeds.",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,37,Police Pursuing this Driver or Police Officer in Pursuit,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,38,Failure to Yield Right-of-Way,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,39,"Failure to Obey Actual Traffic Sign,Traffic Control Devices or Traffic Officers;Failure to Obey Safety Zone Traffic Laws",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,40,Passing Through or Around Barrier,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,41,Failure to Observe Warnings or Instructions on Vehicles Displaying Them,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,42,Failure to Signal Intentions,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,45,Driving Less than Posted Minimum,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,47,Making Right Turn From Left-Turn Lane. Make Left Turn From Right-Turn Lane,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,48,Making Other Improper Turn,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,50,Driving Wrong Way on One-Way Trafficway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,51,Driving on Wrong Side of Two-Way Trafficway (Intentional or Unintentional),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,52,Operator Inexperience,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,53,Unfamiliar with Roadway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,54,Stopped in Roadway (Vehicle Not Abandoned),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,57,Locked Wheel,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,58,Overcorrecting,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,59,Getting Off/Out of or On/In to a Vehicle,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,73,Driver has not complied with Learner`s Permit or Intermediate Driver License Restrictions (GDL Restrictions),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,74,Driver Has Not Complied With Physical or Other Imposed Restrictions (not including GDL Restrictions),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,77,Severe Crosswind,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,78,Wind from Passing Truck,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,79,Slippery or Loose Surface,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,80,Tire Blowout or Flat,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,81,Debris or Objects in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,82,"Ruts, Holes, Bumps in Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,83,Live Animals in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,84,Vehicle in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,85,Phantom Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,86,"Pedestrian, Pedal Cyclist or Other Non-Motorist",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,87,"Ice, Snow, Slush, Water, Sand, Dirt, Oil, Wet Leaves on Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,88,Trailer Fishtailing or swaying,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,89,Driver Has a Driving Record or Driver`s License From More Than One State,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,91,"Non-Traffic Violation Charged - manslaughter, homicide or other assault committed without malice.",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,4,Reaction to or Failure to Take Drugs/Medication,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,6,Careless Driving,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,8,Aggressive Driving / Road Rage,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,12,Mother of Dead Fetus/ Mother of Infant Born Post Crash,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,13,Mentally Challenged,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,15,"Seat Back Not In Normal Upright Position, Seat Back Reclined",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,16,Police or Law Enforcement Officer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,18,Traveling on Prohibited Trafficways,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,19,Legally Driving on Suspended or Revoked License,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,20,Leaving Vehicle Unattended with Engine Running. Leaving Vehicle Unattended in Roadway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,21,Overloading or Improper Loading of Vehicle with Passengers or Cargo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,22,Towing or Pushing Vehicle Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,23,Failing to Dim Lights or to Have Lights on When Required,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,24,Operating without Required Equipment,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,26,Following Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,27,Improper or Erratic Lane Changing,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,28,Failure to keep in Proper Lane,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,29,"Intentional Illegal Driving on Road Shoulder, in Ditch, on Sidewalk or on Median",1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,30,Making Improper Entry to or Exit from Trafficway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,31,Starting or Backing Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,32,Opening Closure into Moving Traffic or While Vehicle is in Motion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,33,"Passing where Prohibited by Posted Signs, Pavement Markings, Hill or Curve, or School Bus Displaying Warning not to Pass",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,34,Passing on Wrong Side,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,35,Passing with Insufficient Distance or Inadequate Visibility or Failing to Yield to Overtaking Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,36,"Operating the Vehicle in an Erratic, Reckless or Negligent Manner, Operating at Erratic or Suddenly Changing Speeds.",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,37,Police Pursuing this Driver or Police Officer in Pursuit,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,38,Failure to Yield Right-of-Way,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,39,"Failure to Obey Actual Traffic Sign,Traffic Control Devices or Traffic Officers;Failure to Obey Safety Zone Traffic Laws",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,40,Passing Through or Around Barrier,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,41,Failure to Observe Warnings or Instructions on Vehicles Displaying Them,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,42,Failure to Signal Intentions,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,45,Driving Less than Posted Minimum,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,47,Making Right Turn From Left-Turn Lane. Make Left Turn From Right-Turn Lane,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,48,Making Other Improper Turn,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,50,Driving Wrong Way on One-Way Trafficway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,51,Driving on Wrong Side of Two-Way Trafficway (Intentional or Unintentional),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,52,Operator Inexperience,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,53,Unfamiliar with Roadway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,54,Stopped in Roadway (Vehicle Not Abandoned),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,57,Locked Wheel,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,58,Overcorrecting,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,59,Getting Off/Out of or On/In to a Vehicle,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,73,Driver has not complied with Learner`s Permit or Intermediate Driver License Restrictions (GDL Restrictions),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,74,Driver Has Not Complied With Physical or Other Imposed Restrictions (not including GDL Restrictions),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,77,Severe Crosswind,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,78,Wind from Passing Truck,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,79,Slippery or Loose Surface,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,80,Tire Blowout or Flat,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,81,Debris or Objects in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,82,"Ruts, Holes, Bumps in Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,83,Live Animals in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,84,Vehicle in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,85,Phantom Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,86,"Pedestrian, Pedal Cyclist or Other Non-Motorist",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,87,"Ice, Snow, Slush, Water, Sand, Dirt, Oil, Wet Leaves on Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,88,Trailer Fishtailing or swaying,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,89,Driver Has a Driving Record or Driver`s License From More Than One State,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,91,"Non-Traffic Violation Charged - manslaughter, homicide or other assault committed without malice.",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,4,Reaction to or Failure to Take Drugs/Medication,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,6,Careless Driving,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,8,Aggressive Driving / Road Rage,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,12,Mother of Dead Fetus/ Mother of Infant Born Post Crash,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,13,Mentally Challenged,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,15,"Seat Back Not In Normal Upright Position, Seat Back Reclined",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,16,Police or Law Enforcement Officer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,18,Traveling on Prohibited Trafficways,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,19,Legally Driving on Suspended or Revoked License,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,20,Leaving Vehicle Unattended with Engine Running. Leaving Vehicle Unattended in Roadway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,21,Overloading or Improper Loading of Vehicle with Passengers or Cargo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,22,Towing or Pushing Vehicle Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,23,Failing to Dim Lights or to Have Lights on When Required,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,24,Operating without Required Equipment,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,26,Following Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,27,Improper or Erratic Lane Changing,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,28,Failure to keep in Proper Lane,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,29,"Intentional Illegal Driving on Road Shoulder, in Ditch, on Sidewalk or on Median",1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,30,Making Improper Entry to or Exit from Trafficway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,31,Starting or Backing Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,32,Opening Closure into Moving Traffic or While Vehicle is in Motion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,33,"Passing where Prohibited by Posted Signs, Pavement Markings, Hill or Curve, or School Bus Displaying Warning not to Pass",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,34,Passing on Wrong Side,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,35,Passing with Insufficient Distance or Inadequate Visibility or Failing to Yield to Overtaking Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,36,"Operating the Vehicle in an Erratic, Reckless or Negligent Manner, Operating at Erratic or Suddenly Changing Speeds.",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,37,Police Pursuing this Driver or Police Officer in Pursuit,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,38,Failure to Yield Right-of-Way,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,39,"Failure to Obey Actual Traffic Sign,Traffic Control Devices or Traffic Officers;Failure to Obey Safety Zone Traffic Laws",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,40,Passing Through or Around Barrier,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,41,Failure to Observe Warnings or Instructions on Vehicles Displaying Them,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,42,Failure to Signal Intentions,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,45,Driving Less than Posted Minimum,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,47,Making Right Turn From Left-Turn Lane. Make Left Turn From Right-Turn Lane,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,48,Making Other Improper Turn,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,50,Driving Wrong Way on One-Way Trafficway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,51,Driving on Wrong Side of Two-Way Trafficway (Intentional or Unintentional),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,52,Operator Inexperience,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,53,Unfamiliar with Roadway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,54,Stopped in Roadway (Vehicle Not Abandoned),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,57,Locked Wheel,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,58,Overcorrecting,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,59,Getting Off/Out of or On/In to a Vehicle,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,73,Driver has not complied with Learner`s Permit or Intermediate Driver License Restrictions (GDL Restrictions),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,74,Driver Has Not Complied With Physical or Other Imposed Restrictions (not including GDL Restrictions),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,77,Severe Crosswind,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,78,Wind from Passing Truck,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,79,Slippery or Loose Surface,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,80,Tire Blowout or Flat,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,81,Debris or Objects in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,82,"Ruts, Holes, Bumps in Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,83,Live Animals in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,84,Vehicle in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,85,Phantom Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,86,"Pedestrian, Pedal Cyclist or Other Non-Motorist",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,87,"Ice, Snow, Slush, Water, Sand, Dirt, Oil, Wet Leaves on Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,88,Trailer Fishtailing or swaying,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,89,Driver Has a Driving Record or Driver`s License From More Than One State,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,91,"Non-Traffic Violation Charged - manslaughter, homicide or other assault committed without malice.",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,4,Reaction to or Failure to Take Drugs/Medication,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,6,Careless Driving,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,8,Aggressive Driving / Road Rage,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,12,Mother of Dead Fetus/ Mother of Infant Born Post Crash,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,13,Mentally Challenged,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,15,"Seat Back Not In Normal Upright Position, Seat Back Reclined",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,16,Police or Law Enforcement Officer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,18,Traveling on Prohibited Trafficways,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,19,Legally Driving on Suspended or Revoked License,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,20,Leaving Vehicle Unattended with Engine Running. Leaving Vehicle Unattended in Roadway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,21,Overloading or Improper Loading of Vehicle with Passengers or Cargo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,22,Towing or Pushing Vehicle Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,23,Failing to Dim Lights or to Have Lights on When Required,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,24,Operating without Required Equipment,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,26,Following Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,27,Improper or Erratic Lane Changing,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,28,Failure to keep in Proper Lane,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,29,"Intentional Illegal Driving on Road Shoulder, in Ditch, on Sidewalk or on Median",1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,30,Making Improper Entry to or Exit from Trafficway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,31,Starting or Backing Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,32,Opening Closure into Moving Traffic or While Vehicle is in Motion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,33,"Passing where Prohibited by Posted Signs, Pavement Markings, Hill or Curve, or School Bus Displaying Warning not to Pass",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,34,Passing on Wrong Side,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,35,Passing with Insufficient Distance or Inadequate Visibility or Failing to Yield to Overtaking Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,36,"Operating the Vehicle in an Erratic, Reckless or Negligent Manner, Operating at Erratic or Suddenly Changing Speeds.",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,37,Police Pursuing this Driver or Police Officer in Pursuit,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,38,Failure to Yield Right-of-Way,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,39,"Failure to Obey Actual Traffic Sign,Traffic Control Devices or Traffic Officers;Failure to Obey Safety Zone Traffic Laws",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,40,Passing Through or Around Barrier,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,41,Failure to Observe Warnings or Instructions on Vehicles Displaying Them,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,42,Failure to Signal Intentions,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,45,Driving Less than Posted Minimum,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,47,Making Right Turn From Left-Turn Lane. Make Left Turn From Right-Turn Lane,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,48,Making Other Improper Turn,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,50,Driving Wrong Way on One-Way Trafficway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,51,Driving on Wrong Side of Two-Way Trafficway (Intentional or Unintentional),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,52,Operator Inexperience,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,53,Unfamiliar with Roadway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,54,Stopped in Roadway (Vehicle Not Abandoned),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,57,Locked Wheel,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,58,Overcorrecting,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,59,Getting Off/Out of or On/In to a Vehicle,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,73,Driver has not complied with Learner`s Permit or Intermediate Driver License Restrictions (GDL Restrictions),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,74,Driver Has Not Complied With Physical or Other Imposed Restrictions (not including GDL Restrictions),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,77,Severe Crosswind,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,78,Wind from Passing Truck,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,79,Slippery or Loose Surface,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,80,Tire Blowout or Flat,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,81,Debris or Objects in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,82,"Ruts, Holes, Bumps in Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,83,Live Animals in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,84,Vehicle in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,85,Phantom Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,86,"Pedestrian, Pedal Cyclist or Other Non-Motorist",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,87,"Ice, Snow, Slush, Water, Sand, Dirt, Oil, Wet Leaves on Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,88,Trailer Fishtailing or swaying,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,89,Driver Has a Driving Record or Driver`s License From More Than One State,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,91,"Non-Traffic Violation Charged - manslaughter, homicide or other assault committed without malice.",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,VTRAFWAY,vtrafway,Trafficway Description,This data element identifies the attribute that best describes the trafficway flow just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,0,Non-Trafficway or Driveway Access,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFWAY,vtrafway,Trafficway Description,This data element identifies the attribute that best describes the trafficway flow just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,1,"Two-Way, Not Divided",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFWAY,vtrafway,Trafficway Description,This data element identifies the attribute that best describes the trafficway flow just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,2,"Two-Way,  Divided, Unprotected (Painted > 4 Feet ) Median",1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,VTRAFWAY,vtrafway,Trafficway Description,This data element identifies the attribute that best describes the trafficway flow just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,3,"Two-Way,  Divided, Positive  Median Barrier",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFWAY,vtrafway,Trafficway Description,This data element identifies the attribute that best describes the trafficway flow just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,4,One-Way Trafficway,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFWAY,vtrafway,Trafficway Description,This data element identifies the attribute that best describes the trafficway flow just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,5,"Two-Way, Not Divided With a Continuous Left-Turn Lane",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFWAY,vtrafway,Trafficway Description,This data element identifies the attribute that best describes the trafficway flow just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,6,Entrance/Exit Ramp,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFWAY,vtrafway,Trafficway Description,This data element identifies the attribute that best describes the trafficway flow just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFWAY,vtrafway,Trafficway Description,This data element identifies the attribute that best describes the trafficway flow just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,VNUM_LAN,vnum_lan,Total Lanes in Roadway,This data element identifies the attribute that best describes the number of travel lanes just prior to this vehicle’s critical precrash event.,"The number of lanes refers to the number of lanes of a continuous cross-section of roadway. For example, a local roadway with one lane going north and one lane going south would be coded as two lanes. However, if a trafficway is a divided highway with two lanes going north, a median, and two lanes going south, then the number of lanes is coded as two. If a trafficway has two lanes going north immediately adjacent to two lanes going south, one continuous cross-section of roadway, then the number of lanes is coded as four. This data element can be used with the Trafficway Description data element VTRAFWAY to determine the trafficway geometry. For example: If (VNUM_LAN= 2) AND (VTRAFWAY=1), then one has a two-lane roadway that is not physically divided, which is what most people think of as a two-lane road (i.e., one lane going in each direction). If the roadway is a divided trafficway, the number of travel lanes counts only lanes in the direction of travel of the first harmful event. If the roadway is an undivided trafficway, the number of travel lanes are all the lanes regardless of their direction of travel. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.",0,Non-Trafficway or Driveway Access,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VNUM_LAN,vnum_lan,Total Lanes in Roadway,This data element identifies the attribute that best describes the number of travel lanes just prior to this vehicle’s critical precrash event.,"The number of lanes refers to the number of lanes of a continuous cross-section of roadway. For example, a local roadway with one lane going north and one lane going south would be coded as two lanes. However, if a trafficway is a divided highway with two lanes going north, a median, and two lanes going south, then the number of lanes is coded as two. If a trafficway has two lanes going north immediately adjacent to two lanes going south, one continuous cross-section of roadway, then the number of lanes is coded as four. This data element can be used with the Trafficway Description data element VTRAFWAY to determine the trafficway geometry. For example: If (VNUM_LAN= 2) AND (VTRAFWAY=1), then one has a two-lane roadway that is not physically divided, which is what most people think of as a two-lane road (i.e., one lane going in each direction). If the roadway is a divided trafficway, the number of travel lanes counts only lanes in the direction of travel of the first harmful event. If the roadway is an undivided trafficway, the number of travel lanes are all the lanes regardless of their direction of travel. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.",1,One lane,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VNUM_LAN,vnum_lan,Total Lanes in Roadway,This data element identifies the attribute that best describes the number of travel lanes just prior to this vehicle’s critical precrash event.,"The number of lanes refers to the number of lanes of a continuous cross-section of roadway. For example, a local roadway with one lane going north and one lane going south would be coded as two lanes. However, if a trafficway is a divided highway with two lanes going north, a median, and two lanes going south, then the number of lanes is coded as two. If a trafficway has two lanes going north immediately adjacent to two lanes going south, one continuous cross-section of roadway, then the number of lanes is coded as four. This data element can be used with the Trafficway Description data element VTRAFWAY to determine the trafficway geometry. For example: If (VNUM_LAN= 2) AND (VTRAFWAY=1), then one has a two-lane roadway that is not physically divided, which is what most people think of as a two-lane road (i.e., one lane going in each direction). If the roadway is a divided trafficway, the number of travel lanes counts only lanes in the direction of travel of the first harmful event. If the roadway is an undivided trafficway, the number of travel lanes are all the lanes regardless of their direction of travel. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.",2,Two lanes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VNUM_LAN,vnum_lan,Total Lanes in Roadway,This data element identifies the attribute that best describes the number of travel lanes just prior to this vehicle’s critical precrash event.,"The number of lanes refers to the number of lanes of a continuous cross-section of roadway. For example, a local roadway with one lane going north and one lane going south would be coded as two lanes. However, if a trafficway is a divided highway with two lanes going north, a median, and two lanes going south, then the number of lanes is coded as two. If a trafficway has two lanes going north immediately adjacent to two lanes going south, one continuous cross-section of roadway, then the number of lanes is coded as four. This data element can be used with the Trafficway Description data element VTRAFWAY to determine the trafficway geometry. For example: If (VNUM_LAN= 2) AND (VTRAFWAY=1), then one has a two-lane roadway that is not physically divided, which is what most people think of as a two-lane road (i.e., one lane going in each direction). If the roadway is a divided trafficway, the number of travel lanes counts only lanes in the direction of travel of the first harmful event. If the roadway is an undivided trafficway, the number of travel lanes are all the lanes regardless of their direction of travel. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.",3,Three lanes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VNUM_LAN,vnum_lan,Total Lanes in Roadway,This data element identifies the attribute that best describes the number of travel lanes just prior to this vehicle’s critical precrash event.,"The number of lanes refers to the number of lanes of a continuous cross-section of roadway. For example, a local roadway with one lane going north and one lane going south would be coded as two lanes. However, if a trafficway is a divided highway with two lanes going north, a median, and two lanes going south, then the number of lanes is coded as two. If a trafficway has two lanes going north immediately adjacent to two lanes going south, one continuous cross-section of roadway, then the number of lanes is coded as four. This data element can be used with the Trafficway Description data element VTRAFWAY to determine the trafficway geometry. For example: If (VNUM_LAN= 2) AND (VTRAFWAY=1), then one has a two-lane roadway that is not physically divided, which is what most people think of as a two-lane road (i.e., one lane going in each direction). If the roadway is a divided trafficway, the number of travel lanes counts only lanes in the direction of travel of the first harmful event. If the roadway is an undivided trafficway, the number of travel lanes are all the lanes regardless of their direction of travel. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.",4,Four lanes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VNUM_LAN,vnum_lan,Total Lanes in Roadway,This data element identifies the attribute that best describes the number of travel lanes just prior to this vehicle’s critical precrash event.,"The number of lanes refers to the number of lanes of a continuous cross-section of roadway. For example, a local roadway with one lane going north and one lane going south would be coded as two lanes. However, if a trafficway is a divided highway with two lanes going north, a median, and two lanes going south, then the number of lanes is coded as two. If a trafficway has two lanes going north immediately adjacent to two lanes going south, one continuous cross-section of roadway, then the number of lanes is coded as four. This data element can be used with the Trafficway Description data element VTRAFWAY to determine the trafficway geometry. For example: If (VNUM_LAN= 2) AND (VTRAFWAY=1), then one has a two-lane roadway that is not physically divided, which is what most people think of as a two-lane road (i.e., one lane going in each direction). If the roadway is a divided trafficway, the number of travel lanes counts only lanes in the direction of travel of the first harmful event. If the roadway is an undivided trafficway, the number of travel lanes are all the lanes regardless of their direction of travel. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.",5,Five lanes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VNUM_LAN,vnum_lan,Total Lanes in Roadway,This data element identifies the attribute that best describes the number of travel lanes just prior to this vehicle’s critical precrash event.,"The number of lanes refers to the number of lanes of a continuous cross-section of roadway. For example, a local roadway with one lane going north and one lane going south would be coded as two lanes. However, if a trafficway is a divided highway with two lanes going north, a median, and two lanes going south, then the number of lanes is coded as two. If a trafficway has two lanes going north immediately adjacent to two lanes going south, one continuous cross-section of roadway, then the number of lanes is coded as four. This data element can be used with the Trafficway Description data element VTRAFWAY to determine the trafficway geometry. For example: If (VNUM_LAN= 2) AND (VTRAFWAY=1), then one has a two-lane roadway that is not physically divided, which is what most people think of as a two-lane road (i.e., one lane going in each direction). If the roadway is a divided trafficway, the number of travel lanes counts only lanes in the direction of travel of the first harmful event. If the roadway is an undivided trafficway, the number of travel lanes are all the lanes regardless of their direction of travel. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.",6,Six lanes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VNUM_LAN,vnum_lan,Total Lanes in Roadway,This data element identifies the attribute that best describes the number of travel lanes just prior to this vehicle’s critical precrash event.,"The number of lanes refers to the number of lanes of a continuous cross-section of roadway. For example, a local roadway with one lane going north and one lane going south would be coded as two lanes. However, if a trafficway is a divided highway with two lanes going north, a median, and two lanes going south, then the number of lanes is coded as two. If a trafficway has two lanes going north immediately adjacent to two lanes going south, one continuous cross-section of roadway, then the number of lanes is coded as four. This data element can be used with the Trafficway Description data element VTRAFWAY to determine the trafficway geometry. For example: If (VNUM_LAN= 2) AND (VTRAFWAY=1), then one has a two-lane roadway that is not physically divided, which is what most people think of as a two-lane road (i.e., one lane going in each direction). If the roadway is a divided trafficway, the number of travel lanes counts only lanes in the direction of travel of the first harmful event. If the roadway is an undivided trafficway, the number of travel lanes are all the lanes regardless of their direction of travel. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.",7,Seven or more lanes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VNUM_LAN,vnum_lan,Total Lanes in Roadway,This data element identifies the attribute that best describes the number of travel lanes just prior to this vehicle’s critical precrash event.,"The number of lanes refers to the number of lanes of a continuous cross-section of roadway. For example, a local roadway with one lane going north and one lane going south would be coded as two lanes. However, if a trafficway is a divided highway with two lanes going north, a median, and two lanes going south, then the number of lanes is coded as two. If a trafficway has two lanes going north immediately adjacent to two lanes going south, one continuous cross-section of roadway, then the number of lanes is coded as four. This data element can be used with the Trafficway Description data element VTRAFWAY to determine the trafficway geometry. For example: If (VNUM_LAN= 2) AND (VTRAFWAY=1), then one has a two-lane roadway that is not physically divided, which is what most people think of as a two-lane road (i.e., one lane going in each direction). If the roadway is a divided trafficway, the number of travel lanes counts only lanes in the direction of travel of the first harmful event. If the roadway is an undivided trafficway, the number of travel lanes are all the lanes regardless of their direction of travel. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.",8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VNUM_LAN,vnum_lan,Total Lanes in Roadway,This data element identifies the attribute that best describes the number of travel lanes just prior to this vehicle’s critical precrash event.,"The number of lanes refers to the number of lanes of a continuous cross-section of roadway. For example, a local roadway with one lane going north and one lane going south would be coded as two lanes. However, if a trafficway is a divided highway with two lanes going north, a median, and two lanes going south, then the number of lanes is coded as two. If a trafficway has two lanes going north immediately adjacent to two lanes going south, one continuous cross-section of roadway, then the number of lanes is coded as four. This data element can be used with the Trafficway Description data element VTRAFWAY to determine the trafficway geometry. For example: If (VNUM_LAN= 2) AND (VTRAFWAY=1), then one has a two-lane roadway that is not physically divided, which is what most people think of as a two-lane road (i.e., one lane going in each direction). If the roadway is a divided trafficway, the number of travel lanes counts only lanes in the direction of travel of the first harmful event. If the roadway is an undivided trafficway, the number of travel lanes are all the lanes regardless of their direction of travel. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.",9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,0,No Statutory Limit/Non-Trafficway or Driveway Access,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,5,5 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,10,10 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,15,15 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,20,20 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,25,25 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,30,30 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,35,35 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,40,40 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,45,45 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,50,50 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,55,55 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,60,60 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,65,65 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,70,70 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,75,75 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,80,80 MPH,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,VALIGN,valign,Roadway Alignment,This data element identifies the attribute that best represents the roadway alignment prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,0,Non-Trafficway or Driveway Access,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VALIGN,valign,Roadway Alignment,This data element identifies the attribute that best represents the roadway alignment prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,1,Straight,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VALIGN,valign,Roadway Alignment,This data element identifies the attribute that best represents the roadway alignment prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,2,Curve Right,1,1,1,1,NA,NA,NA,NA,NA,1
FARS,vehicle,VALIGN,valign,Roadway Alignment,This data element identifies the attribute that best represents the roadway alignment prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,3,Curve Left,1,1,1,1,NA,NA,NA,NA,NA,1
FARS,vehicle,VALIGN,valign,Roadway Alignment,This data element identifies the attribute that best represents the roadway alignment prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,4,Curve - Unknown Direction,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VALIGN,valign,Roadway Alignment,This data element identifies the attribute that best represents the roadway alignment prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VALIGN,valign,Roadway Alignment,This data element identifies the attribute that best represents the roadway alignment prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,VPROFILE,vprofile,Roadway Grade,This data element identifies the attribute that best represents the roadway grade prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level. Prior to 2010 this data element’s name was Roadway Profile.,0,Non-Trafficway or Driveway Access,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPROFILE,vprofile,Roadway Grade,This data element identifies the attribute that best represents the roadway grade prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level. Prior to 2010 this data element’s name was Roadway Profile.,1,Level,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPROFILE,vprofile,Roadway Grade,This data element identifies the attribute that best represents the roadway grade prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level. Prior to 2010 this data element’s name was Roadway Profile.,2,"Grade, Unknown Slope",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPROFILE,vprofile,Roadway Grade,This data element identifies the attribute that best represents the roadway grade prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level. Prior to 2010 this data element’s name was Roadway Profile.,3,Hillcrest,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPROFILE,vprofile,Roadway Grade,This data element identifies the attribute that best represents the roadway grade prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level. Prior to 2010 this data element’s name was Roadway Profile.,4,Sag (Bottom),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPROFILE,vprofile,Roadway Grade,This data element identifies the attribute that best represents the roadway grade prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level. Prior to 2010 this data element’s name was Roadway Profile.,5,Uphill,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPROFILE,vprofile,Roadway Grade,This data element identifies the attribute that best represents the roadway grade prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level. Prior to 2010 this data element’s name was Roadway Profile.,6,Downhill,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPROFILE,vprofile,Roadway Grade,This data element identifies the attribute that best represents the roadway grade prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level. Prior to 2010 this data element’s name was Roadway Profile.,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPROFILE,vprofile,Roadway Grade,This data element identifies the attribute that best represents the roadway grade prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level. Prior to 2010 this data element’s name was Roadway Profile.,9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,VPAVETYP,vpavetyp,Roadway Surface Type,This data element identifies the attribute that best represents the roadway surface type prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,0,Non-Trafficway or Driveway Access,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPAVETYP,vpavetyp,Roadway Surface Type,This data element identifies the attribute that best represents the roadway surface type prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,1,Concrete,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPAVETYP,vpavetyp,Roadway Surface Type,This data element identifies the attribute that best represents the roadway surface type prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,2,"Blacktop, Bituminous, or Asphalt",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPAVETYP,vpavetyp,Roadway Surface Type,This data element identifies the attribute that best represents the roadway surface type prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,3,Brick or Block,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPAVETYP,vpavetyp,Roadway Surface Type,This data element identifies the attribute that best represents the roadway surface type prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,4,"Slag, Gravel or Stone",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPAVETYP,vpavetyp,Roadway Surface Type,This data element identifies the attribute that best represents the roadway surface type prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,5,Dirt,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPAVETYP,vpavetyp,Roadway Surface Type,This data element identifies the attribute that best represents the roadway surface type prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,7,Other,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPAVETYP,vpavetyp,Roadway Surface Type,This data element identifies the attribute that best represents the roadway surface type prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VPAVETYP,vpavetyp,Roadway Surface Type,This data element identifies the attribute that best represents the roadway surface type prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,0,Non-Trafficway or Driveway Access,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,1,Dry,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,2,Wet,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,3,Snow,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,4,Ice/Frost,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,5,Sand,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,6,Water (Standing or Moving),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,7,Oil,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,8,Other,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,10,Slush,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,11,"Mud, Dirt or Gravel",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,0,No Controls,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,1,Traffic control signal (on colors) without Pedestrian Signal,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,2,Traffic control signal (on colors) with Pedestrian Signal,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,3,Traffic control signal(on colors) not known whether or not Pedestrian Signal,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,4,Flashing Traffic Control Signal,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,7,Lane Use Control Signal,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,8,Other Highway Traffic Signal,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,9,Unknown Highway Traffic Signal,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,20,Stop Sign,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,21,Yield Sign,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,23,School Zone Sign/Device,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,28,Other Regulatory Sign,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,29,Unknown Regulatory Sign,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,40,Warning Sign,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,50,Person,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,65,Railway Crossing Device,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,97,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,98,Other,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,VTCONT_F,vtcont_f,Traffic Control Device Functioning,This data element identifies the functionality of the traffic control device recorded for this vehicle in the data element “Traffic Control Device.”,Data not collected prior to 1982. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,0,No Controls,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTCONT_F,vtcont_f,Traffic Control Device Functioning,This data element identifies the functionality of the traffic control device recorded for this vehicle in the data element “Traffic Control Device.”,Data not collected prior to 1982. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,1,Device Not Functioning,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTCONT_F,vtcont_f,Traffic Control Device Functioning,This data element identifies the functionality of the traffic control device recorded for this vehicle in the data element “Traffic Control Device.”,Data not collected prior to 1982. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,2,Device Functioning-Functioning Improperly,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTCONT_F,vtcont_f,Traffic Control Device Functioning,This data element identifies the functionality of the traffic control device recorded for this vehicle in the data element “Traffic Control Device.”,Data not collected prior to 1982. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,3,Device Functioning Properly,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTCONT_F,vtcont_f,Traffic Control Device Functioning,This data element identifies the functionality of the traffic control device recorded for this vehicle in the data element “Traffic Control Device.”,Data not collected prior to 1982. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,VTCONT_F,vtcont_f,Traffic Control Device Functioning,This data element identifies the functionality of the traffic control device recorded for this vehicle in the data element “Traffic Control Device.”,Data not collected prior to 1982. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,0,No Driver Present / Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,1,Going Straight,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,2,Decelerating in Road,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,3,Accelerating in Road,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,4,Starting in Road,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,5,Stopped in Roadway,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,6,Passing or Overtaking Another Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,7,"Disabled or ""Parked"" in Travel lane",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,8,Leaving a Parking Position,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,9,Entering a Parking Position,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,10,Turning Right,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,11,Turning Left,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,12,Making a U-turn,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,13,Backing Up (other than for Parking Position),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,14,Negotiating a Curve,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,15,Changing Lanes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,16,Merging,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,17,Successful Avoidance Maneuver to a Previous Critical Event,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,98,Other(specify:),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH1,p_crash1,Pre-Event Movement,This data element identifies the attribute that best describes this vehicle’s activity prior to the driver’s realization of an impending critical event or just prior to impact if the driver took no action or had no time to attempt any evasive maneuvers.,NA,99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,1,Blow out/flat tire,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,2,Stalled engine,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,3,"Disabling vehicle failure (e.g., wheel fell off) (specify:)",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,4,"Non-disabling vehicle problem (e.g., hood flew up)(specify:)",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,5,"Poor road conditions (puddle, pothole, ice, etc.) (Specify:)",1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,6,Traveling too fast for conditions,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,8,Other cause of control loss (specify:),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,9,Unknown cause of control loss,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,10,Over the lane line on left side of travel lane,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,11,Over the lane line on right side of travel lane,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,12,Off the edge of the road on the left side,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,13,Off the edge of the road on the right side,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,14,End departure,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,15,Turning left at junction,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,16,Turning right at junction,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,17,Crossing over (passing through) intersection,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,18,This vehicle decelerating,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,19,Unknown travel direction,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,50,Other vehicle stopped,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,51,Traveling in same direction with lower or steady speed,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,52,Traveling in same direction while decelerating,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,53,Traveling in same direction with higher speed,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,54,Traveling in opposite direction,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,55,In crossover,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,56,Backing,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,59,Unknown travel direction of the other motor vehicle in lane,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,60,From adjacent lane (same direction) over left lane line,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,61,From adjacent lane (same direction) over right lane line,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,62,From opposite direction  over left lane line,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,63,From opposite direction  over right lane line,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,64,"From parking lane, median, shoulder, roadside",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,65,"From crossing street, turning into same direction",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,66,"From crossing street, across path",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,67,"From crossing street, turning into opposite direction",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,68,"From crossing street, intended path not known",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,70,"From driveway, turning into same direction",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,71,"From driveway, across path",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,72,"From driveway, turning into opposite direction",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,73,"From driveway, intended path not known",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,74,From entrance to limited access highway,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,78,Encroachment by other vehicle - details unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,80,Pedestrian in road,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,81,Pedestrian approaching road,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,82,Pedestrian unknown location,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,83,Pedalcyclist or other non-motorist in road,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,84,Pedalcyclist or other non-motorist approaching road,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,85,Pedalcyclist or other non-motorist unknown location,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,87,Animal in road,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,88,Animal approaching road,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,89,Animal -unknown location,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,90,Object in road,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,91,Object approaching road,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,92,Object unknown location,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,98,Other critical precrash event (specify:),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,0,No Driver Present / Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,1,No Avoidance Maneuver,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,2,Braking (no lockup),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,3,Braking (lockup),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,4,Braking (lockup unknown),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,5,Releasing brakes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,6,Steering left,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,7,Steering right,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,8,Braking and steering left,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,9,Braking and steering right,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,10,Accelerating,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,11,Accelerating and steering left,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,12,Accelerating and steering right,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,98,Other actions (specify:),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,99,Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,PCRASH4,pcrash4,Pre- Impact Stability,"This data element identifies the attribute that best describes the stability of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,0,No Driver Present / Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH4,pcrash4,Pre- Impact Stability,"This data element identifies the attribute that best describes the stability of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,1,Tracking,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH4,pcrash4,Pre- Impact Stability,"This data element identifies the attribute that best describes the stability of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,2,Skidding longitudinally  rotation less than 30 degrees,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH4,pcrash4,Pre- Impact Stability,"This data element identifies the attribute that best describes the stability of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,3,Skidding laterally clockwise rotation,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH4,pcrash4,Pre- Impact Stability,"This data element identifies the attribute that best describes the stability of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,4,Skidding laterally counterclockwise rotation,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH4,pcrash4,Pre- Impact Stability,"This data element identifies the attribute that best describes the stability of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,5,"Skidding Laterally, Rotation Direction Unknown",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH4,pcrash4,Pre- Impact Stability,"This data element identifies the attribute that best describes the stability of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,7,Other vehicle loss-of-control (specify:),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH4,pcrash4,Pre- Impact Stability,"This data element identifies the attribute that best describes the stability of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,9,Precrash stability unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH5,pcrash5,Pre- Impact Location,"This data element identifies the attribute that best describes the location of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,0,No Driver Present / Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH5,pcrash5,Pre- Impact Location,"This data element identifies the attribute that best describes the location of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,1,Stayed in original travel lane,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH5,pcrash5,Pre- Impact Location,"This data element identifies the attribute that best describes the location of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,2,"Stayed on roadway, but left original travel lane",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH5,pcrash5,Pre- Impact Location,"This data element identifies the attribute that best describes the location of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,3,"Stayed on roadway, not known if left original travel lane",1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH5,pcrash5,Pre- Impact Location,"This data element identifies the attribute that best describes the location of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,4,Departed roadway,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH5,pcrash5,Pre- Impact Location,"This data element identifies the attribute that best describes the location of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,5,Remained off roadway,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH5,pcrash5,Pre- Impact Location,"This data element identifies the attribute that best describes the location of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,6,Returned to roadway,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH5,pcrash5,Pre- Impact Location,"This data element identifies the attribute that best describes the location of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,7,Entered roadway,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,PCRASH5,pcrash5,Pre- Impact Location,"This data element identifies the attribute that best describes the location of this vehicle after the “Critical Precrash Event,” but before the impact.",NA,9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,0,No Impact,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,1,Drive Off Road,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,2,Control/Traction Loss,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,3,"Avoid Collision With Veh., Ped., Anim.",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,4,Specifics Other,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,5,Specifics Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,6,Drive Off Road,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,7,Control/Traction Loss,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,8,"Avoid Collision With Veh., Ped., Anim.",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,9,Specifics Other,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,10,Specifics Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,11,Parked Veh.,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,12,Sta. Object,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,13,Pedestrian/ Animal,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,14,End Departure,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,15,Specifics Other,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,16,Specifics Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,20,Stopped,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,21,"Stopped, Straight",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,22,"Stopped, Left",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,23,"Stopped, Right",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,24,Slower,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,25,"Slower, Going Straight",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,26,"Slower, Going Left",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,27,"Slower, Going Right",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,28,Decelerating (Slowing),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,29,"Decelerating (Slowing), Going Straight",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,30,"Decelerating (Slowing), Going Left",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,31,"Decelerating (Slowing), Going Right",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,32,Specifics Other,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,33,Specifics Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,34,Control/Traction Loss,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,35,Control/Traction Loss,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,36,Control/Traction Loss,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,37,Control/Traction Loss,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,38,Avoid Collision with Vehicle,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,39,Avoid Collision with Vehicle,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,40,Avoid Collision With Object,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,41,Avoid Collision With Object,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,42,Specifics Other,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,43,Specifics Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,44,Straight Ahead on Left,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,45,Straight Ahead on Left/Right,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,46,Changing Lanes to the Right,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,47,Changing Lanes to the Left,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,48,Specifics Other,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,49,Specifics Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,50,Lateral Move (Left/Right),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,51,Lateral Move (Going Straight),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,52,Specifics Other,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,53,Specifics Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,54,Control/Traction Loss,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,55,Control/Traction Loss,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,56,Control/Traction Loss,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,57,Control/Traction Loss,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,58,Avoid Collision With Vehicle,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,59,Avoid Collision With Vehicle,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,60,Avoid Collision With Object,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,61,Avoid Collision With Object,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,62,Specifics Other,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,63,Specifics Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,64,Lateral Move (Left/Right),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,65,Lateral Move (Going Straight),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,66,Specifics Other,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,67,Specifics Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,68,Initial Opposite Directions (Left/Right),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,69,Initial Opposite Directions (Going Straight),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,70,Initial Same Directions (Turning Right),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,71,Initial Same Directions (Going Straight),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,72,Initial Same Directions (Turning Left),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,73,Initial Same Directions (Going Straight),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,74,Specifics Other,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,75,Specifics Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,76,Turn Into Same Direction (Turning Left),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,77,Turn Into Same Direction (Going Straight),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,78,Turn Into Same Direction (Turning Right),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,79,Turn Into Same Direction (Going Straight),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,80,Turn Into Opposite Directions (Turning Right),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,81,Turn Into Opposite Directions (Going Straight),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,82,Turn Into Opposite Directions (Turning Left),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,83,Turn Into Opposite Directions (Going Straight),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,84,Specifics Other,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,85,Specifics Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,86,Striking from the Right,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,87,Struck on the Right,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,88,Striking from the Left,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,89,Struck on the left,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,90,Specifics Other,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,91,Specifics Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,92,Backing Vehicle,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,93,Other Vehicle,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,98,Other Crash Type,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,99,Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,DEATHS,deaths,Fatals in Vehicle,This data element records the number of fatalities that occurred in this vehicle.,The data element is derived by counting all people with “Injury Severity” of 4 in the vehicle. The data element “Fatalities” in the Accident data file provides the number of deaths for the entire crash. This is a derived data element and is not coded on the form directly. In 1976 this value was always set to 0. This data element also appears in the Parkwork data file as PDEATHS.,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_DRINK,dr_drink,Driver Drinking,This data element records whether the driver was drinking.,"This data element is derived from data elements in the Vehicle and Person data files. Data are analyzed and if there is ""sufficient information"" to conclude that a driver was drinking, i.e., positive BAC data or police-reported alcohol involvement, then a driver is classified as drinking. A driver is classified as drinking (alcohol-involved) if the driver has (1) police-reported alcohol involvement, or (2) a positive alcohol test result. A driver who is charged with an alcohol violation does not by itself make the driver a ""drinking driver"" by this definition. Note that alcohol data is often missing. For that reason, this data element may under-count the actual number of drinking drivers.",0,No,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_DRINK,dr_drink,Driver Drinking,This data element records whether the driver was drinking.,"This data element is derived from data elements in the Vehicle and Person data files. Data are analyzed and if there is ""sufficient information"" to conclude that a driver was drinking, i.e., positive BAC data or police-reported alcohol involvement, then a driver is classified as drinking. A driver is classified as drinking (alcohol-involved) if the driver has (1) police-reported alcohol involvement, or (2) a positive alcohol test result. A driver who is charged with an alcohol violation does not by itself make the driver a ""drinking driver"" by this definition. Note that alcohol data is often missing. For that reason, this data element may under-count the actual number of drinking drivers.",1,Yes,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_DRINK,dr_drink,Driver Drinking,This data element records whether the driver was drinking.,"This data element is derived from data elements in the Vehicle and Person data files. Data are analyzed and if there is ""sufficient information"" to conclude that a driver was drinking, i.e., positive BAC data or police-reported alcohol involvement, then a driver is classified as drinking. A driver is classified as drinking (alcohol-involved) if the driver has (1) police-reported alcohol involvement, or (2) a positive alcohol test result. A driver who is charged with an alcohol violation does not by itself make the driver a ""drinking driver"" by this definition. Note that alcohol data is often missing. For that reason, this data element may under-count the actual number of drinking drivers.",8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_DRINK,dr_drink,Driver Drinking,This data element records whether the driver was drinking.,"This data element is derived from data elements in the Vehicle and Person data files. Data are analyzed and if there is ""sufficient information"" to conclude that a driver was drinking, i.e., positive BAC data or police-reported alcohol involvement, then a driver is classified as drinking. A driver is classified as drinking (alcohol-involved) if the driver has (1) police-reported alcohol involvement, or (2) a positive alcohol test result. A driver who is charged with an alcohol violation does not by itself make the driver a ""drinking driver"" by this definition. Note that alcohol data is often missing. For that reason, this data element may under-count the actual number of drinking drivers.",9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,person,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,person,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,person,PER_NO,per_no,Person Number,"This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files.","Each occupant of the vehicle is numbered, and each non-occupant is numbered; in the case of a non-occupant the vehicle number is zero. The numbers for occupants are consecutive for each vehicle beginning with 1. Numbers are never skipped. Drivers do not have to be coded 1. Non- Occupants are identified by vehicle number 0 and are numbered consecutively starting with 1 for each non-motorist. To get drivers see data element PER_TYP under Person Type. PER_NO can be used in merges, e.g., when merging the FARS person data file with the multiple cause of death file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,person,STR_VEH,str_veh,Number Of Motor Vehicle Striking Non-Motorist,This data element identifies the “Vehicle Number” (VEH_NO) of the motor vehicle in-transport that made contact with this non-motorist.,"This data element applies only to non-motorists/non-occupants and reflects the vehicle that made contact with the non-motorist/non-occupant identified by the Person Number (PER_NO). The number must match the vehicle number of the striking vehicle. This number is similar to VEH_NO, except that the non-motorist/non-occupant was struck by the vehicle, rather than being within the vehicle. If a non-motorist is hit as a result of a vehicle-to-vehicle collision and it could not be determined which vehicle struck the non-motorist, the lowest vehicle number of the vehicle involved is used. In the element Related Factors – Person Level, the attribute 31 (Default Code Used for Vehicle Numbering) will be coded.",NA,(Self-evident),1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,0,Less than One Year,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,1,1 Year,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,2,2 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,3,3 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,4,4 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,5,5 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,6,6 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,7,7 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,8,8 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,9,9 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,10,10 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,11,11 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,12,12 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,13,13 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,14,14 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,15,15 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,16,16 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,17,17 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,18,18 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,19,19 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,20,20 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,21,21 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,22,22 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,23,23 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,24,24 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,25,25 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,26,26 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,27,27 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,28,28 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,29,29 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,30,30 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,31,31 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,32,32 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,33,33 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,34,34 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,35,35 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,36,36 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,37,37 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,38,38 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,39,39 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,40,40 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,41,41 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,42,42 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,43,43 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,44,44 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,45,45 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,46,46 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,47,47 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,48,48 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,49,49 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,50,50 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,51,51 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,52,52 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,53,53 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,54,54 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,55,55 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,56,56 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,57,57 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,58,58 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,59,59 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,60,60 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,61,61 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,62,62 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,63,63 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,64,64 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,65,65 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,66,66 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,67,67 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,68,68 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,69,69 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,70,70 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,71,71 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,72,72 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,73,73 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,74,74 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,75,75 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,76,76 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,77,77 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,78,78 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,79,79 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,80,80 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,81,81 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,82,82 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,83,83 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,84,84 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,85,85 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,86,86 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,87,87 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,88,88 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,89,89 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,90,90 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,91,91 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,92,92 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,93,93 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,94,94 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,95,95 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,96,96 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,97,97 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,98,98 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,99,99 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,100,100 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,101,101 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,102,102 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,103,103 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,104,104 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,105,105 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,106,106 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,107,107 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,108,108 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,109,109 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,110,110 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,111,111 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,112,112 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,113,113 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,114,114 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,115,115 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,116,116 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,117,117 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,118,118 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,119,119 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,120,120 Years,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,998,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,999,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,SEX,sex,Sex,This data element identifies the sex of this person involved in the crash.,"From 1975 to 1981, if no information was known about the hit-and-run vehicle and/or driver, then neither the vehicle form nor the driver form was filled out and were not counted in the FARS census. Starting in 1982 both a vehicle and a driver form were filled out and the data were identified as unknown. This is why there were approximately only 20 to 40 drivers with unknown sex listed in the FARS data file from 1975 to 1981 and 700 to 1000 drivers with unknown sex from 1982 on. On March 22, 1995, a quick review of the 1994 Annual Report File revealed that of the 768 people in the 1994 data file with unknown sex; over 90 percent were involved in hit-and-run crashes.",1,Male,1,1,1,1,1,1,1,1,1,1
FARS,person,SEX,sex,Sex,This data element identifies the sex of this person involved in the crash.,"From 1975 to 1981, if no information was known about the hit-and-run vehicle and/or driver, then neither the vehicle form nor the driver form was filled out and were not counted in the FARS census. Starting in 1982 both a vehicle and a driver form were filled out and the data were identified as unknown. This is why there were approximately only 20 to 40 drivers with unknown sex listed in the FARS data file from 1975 to 1981 and 700 to 1000 drivers with unknown sex from 1982 on. On March 22, 1995, a quick review of the 1994 Annual Report File revealed that of the 768 people in the 1994 data file with unknown sex; over 90 percent were involved in hit-and-run crashes.",2,Female,1,1,1,1,1,1,1,1,1,1
FARS,person,SEX,sex,Sex,This data element identifies the sex of this person involved in the crash.,"From 1975 to 1981, if no information was known about the hit-and-run vehicle and/or driver, then neither the vehicle form nor the driver form was filled out and were not counted in the FARS census. Starting in 1982 both a vehicle and a driver form were filled out and the data were identified as unknown. This is why there were approximately only 20 to 40 drivers with unknown sex listed in the FARS data file from 1975 to 1981 and 700 to 1000 drivers with unknown sex from 1982 on. On March 22, 1995, a quick review of the 1994 Annual Report File revealed that of the 768 people in the 1994 data file with unknown sex; over 90 percent were involved in hit-and-run crashes.",8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,person,SEX,sex,Sex,This data element identifies the sex of this person involved in the crash.,"From 1975 to 1981, if no information was known about the hit-and-run vehicle and/or driver, then neither the vehicle form nor the driver form was filled out and were not counted in the FARS census. Starting in 1982 both a vehicle and a driver form were filled out and the data were identified as unknown. This is why there were approximately only 20 to 40 drivers with unknown sex listed in the FARS data file from 1975 to 1981 and 700 to 1000 drivers with unknown sex from 1982 on. On March 22, 1995, a quick review of the 1994 Annual Report File revealed that of the 768 people in the 1994 data file with unknown sex; over 90 percent were involved in hit-and-run crashes.",9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,1,Driver of a Motor Vehicle In-Transport,1,1,1,1,1,1,1,1,1,1
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,2,Passenger of a Motor Vehicle In-Transport,1,1,1,1,1,1,1,1,1,1
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,3,Occupant of a Motor Vehicle Not In- Transport,1,1,1,1,1,1,1,1,1,1
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,4,Occupant of a Non-Motor Vehicle Transport Device,1,1,1,1,1,1,1,1,1,1
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,5,Pedestrian,1,1,1,1,1,1,1,1,1,1
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,6,Bicyclist,1,1,1,1,1,1,1,1,1,1
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,7,Other Cyclist,1,1,1,1,1,1,1,1,NA,NA
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,8,Persons on Personal Conveyances,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,9,Unknown Occupant Type in a Motor Vehicle In- Transport,1,1,1,1,1,1,1,1,1,1
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,10,Persons In/On Buildings,1,1,1,1,1,1,1,1,NA,NA
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,19,Unknown Type of Non-Motorist,1,1,1,1,1,1,1,1,1,1
FARS,person,INJ_SEV,inj_sev,Injury Severity,This data element describes the severity of the injury to this person in the crash using the KABCO scale.,It is important to realize that some States do not always collect data on people who were in a crash but were not injured. If the analysis being performed depends on non-injured occupants— for example some paired comparisons—check the data at the State level. Prior to 2022 the Data Element ID was P8/NM8.,0,No Apparent Injury (O),1,1,1,1,1,1,1,1,1,1
FARS,person,INJ_SEV,inj_sev,Injury Severity,This data element describes the severity of the injury to this person in the crash using the KABCO scale.,It is important to realize that some States do not always collect data on people who were in a crash but were not injured. If the analysis being performed depends on non-injured occupants— for example some paired comparisons—check the data at the State level. Prior to 2022 the Data Element ID was P8/NM8.,1,Possible Injury (C),1,1,1,1,1,1,1,1,1,1
FARS,person,INJ_SEV,inj_sev,Injury Severity,This data element describes the severity of the injury to this person in the crash using the KABCO scale.,It is important to realize that some States do not always collect data on people who were in a crash but were not injured. If the analysis being performed depends on non-injured occupants— for example some paired comparisons—check the data at the State level. Prior to 2022 the Data Element ID was P8/NM8.,2,Suspected Minor Injury(B),1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,person,INJ_SEV,inj_sev,Injury Severity,This data element describes the severity of the injury to this person in the crash using the KABCO scale.,It is important to realize that some States do not always collect data on people who were in a crash but were not injured. If the analysis being performed depends on non-injured occupants— for example some paired comparisons—check the data at the State level. Prior to 2022 the Data Element ID was P8/NM8.,3,Suspected Serious Injury(A),1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,person,INJ_SEV,inj_sev,Injury Severity,This data element describes the severity of the injury to this person in the crash using the KABCO scale.,It is important to realize that some States do not always collect data on people who were in a crash but were not injured. If the analysis being performed depends on non-injured occupants— for example some paired comparisons—check the data at the State level. Prior to 2022 the Data Element ID was P8/NM8.,4,Fatal Injury (K),1,1,1,1,1,1,1,1,1,1
FARS,person,INJ_SEV,inj_sev,Injury Severity,This data element describes the severity of the injury to this person in the crash using the KABCO scale.,It is important to realize that some States do not always collect data on people who were in a crash but were not injured. If the analysis being performed depends on non-injured occupants— for example some paired comparisons—check the data at the State level. Prior to 2022 the Data Element ID was P8/NM8.,5,"Injured, Severity Unknown",1,1,1,1,1,1,1,1,1,1
FARS,person,INJ_SEV,inj_sev,Injury Severity,This data element describes the severity of the injury to this person in the crash using the KABCO scale.,It is important to realize that some States do not always collect data on people who were in a crash but were not injured. If the analysis being performed depends on non-injured occupants— for example some paired comparisons—check the data at the State level. Prior to 2022 the Data Element ID was P8/NM8.,6,Died Prior to Crash*,1,1,1,1,1,1,1,1,1,1
FARS,person,INJ_SEV,inj_sev,Injury Severity,This data element describes the severity of the injury to this person in the crash using the KABCO scale.,It is important to realize that some States do not always collect data on people who were in a crash but were not injured. If the analysis being performed depends on non-injured occupants— for example some paired comparisons—check the data at the State level. Prior to 2022 the Data Element ID was P8/NM8.,9,Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,0,Not a Motor Vehicle Occupant,1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,11,"Front Seat, Left Side",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,12,"Front Seat, Middle",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,13,"Front Seat, Right Side",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,18,"Front Seat, Other",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,19,"Front Seat, Unknown",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,21,"Second Seat, Left Side",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,22,"Second Seat, Middle",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,23,"Second Seat, Right Side",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,28,"Second Seat, Other",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,29,"Second Seat, Unknown",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,31,"Third Seat, Left Side",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,32,"Third Seat, Middle",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,33,"Third Seat, Right Side",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,38,"Third Seat, Other",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,39,"Third Seat, Unknown",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,41,"Fourth Seat, Left Side",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,42,"Fourth Seat, Middle",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,43,"Fourth Seat, Right Side",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,48,"Fourth Seat, Other",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,49,"Fourth Seat, Unknown",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,50,Sleeper Section of Cab (Truck),1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,51,Other Passenger in enclosed passenger or cargo area,1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,52,Other Passenger in unenclosed passenger or cargo area,1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,53,"Other Passenger in passenger or cargo area, unknown whether or not enclosed",1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,54,Trailing Unit,1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,55,Riding on Exterior of Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",0,Not Applicable,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",1,Shoulder Belt Only Used,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",2,Lap Belt Only Used,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",3,Shoulder and Lap Belt Used,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",4,Child Restraint Type Unknown,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",5,DOT-Compliant Motorcycle Helmet,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",7,None Used,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",8,Restraint Used - Type Unknown,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",10,Child Restraint System - Forward Facing,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",11,Child Restraint System  - Rear Facing,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",12,Booster Seat,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",16,"Helmet, Other than DOT-Compliant Motorcycle Helmet",1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",17,No Helmet,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",19,"Helmet, Unknown if DOT Compliant",1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",29,Unknown if Helmet Worn,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",96,Not a Motor Vehicle Occupant,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",97,Other,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",98,Not Reported,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,REST_MIS,rest_mis,Any Indication of Mis-Use of Restraint System/Helmet Use,This data element identifies any misuse of the available restraint system used by this person.,"Prior to 2019 this data element’s name was “Indication of Misuse of Restraint System/Helmet” that included helmet misuse, and the Data Element ID was P11. Starting in 2019 helmet misuse is captured as part of the data element “Indication of Helmet Misuse.”",0,No,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_MIS,rest_mis,Any Indication of Mis-Use of Restraint System/Helmet Use,This data element identifies any misuse of the available restraint system used by this person.,"Prior to 2019 this data element’s name was “Indication of Misuse of Restraint System/Helmet” that included helmet misuse, and the Data Element ID was P11. Starting in 2019 helmet misuse is captured as part of the data element “Indication of Helmet Misuse.”",1,Yes,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,REST_MIS,rest_mis,Any Indication of Mis-Use of Restraint System/Helmet Use,This data element identifies any misuse of the available restraint system used by this person.,"Prior to 2019 this data element’s name was “Indication of Misuse of Restraint System/Helmet” that included helmet misuse, and the Data Element ID was P11. Starting in 2019 helmet misuse is captured as part of the data element “Indication of Helmet Misuse.”",8,Not a Motor Vehicle Occupant,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,AIR_BAG,air_bag,Air Bag Deployed,This data element records air bag availability and deployment for this person as reported in the case material.,"This data element is designed to collect both air bag availability and deployment for each occupied seat position. Variation in the presentation of the source data on the State crash report forms and the selections coded on the police crash report may produce unlikely combinations or missing data. For example:    1. If the seat position does not have an air bag at the time of manufacture, but the       information on the police crash report indicates an air bag was available or deployed, the       information on the police crash report may have taken precedence.    2. If the seat position has an air bag installed at the time of manufacture and the police crash       report indicates there is no air bag available, then the police crash report information may       have taken precedence.",0,Not Applicable,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,person,AIR_BAG,air_bag,Air Bag Deployed,This data element records air bag availability and deployment for this person as reported in the case material.,"This data element is designed to collect both air bag availability and deployment for each occupied seat position. Variation in the presentation of the source data on the State crash report forms and the selections coded on the police crash report may produce unlikely combinations or missing data. For example:    1. If the seat position does not have an air bag at the time of manufacture, but the       information on the police crash report indicates an air bag was available or deployed, the       information on the police crash report may have taken precedence.    2. If the seat position has an air bag installed at the time of manufacture and the police crash       report indicates there is no air bag available, then the police crash report information may       have taken precedence.",1,Deployed- Front,1,1,1,1,1,1,1,1,1,1
FARS,person,AIR_BAG,air_bag,Air Bag Deployed,This data element records air bag availability and deployment for this person as reported in the case material.,"This data element is designed to collect both air bag availability and deployment for each occupied seat position. Variation in the presentation of the source data on the State crash report forms and the selections coded on the police crash report may produce unlikely combinations or missing data. For example:    1. If the seat position does not have an air bag at the time of manufacture, but the       information on the police crash report indicates an air bag was available or deployed, the       information on the police crash report may have taken precedence.    2. If the seat position has an air bag installed at the time of manufacture and the police crash       report indicates there is no air bag available, then the police crash report information may       have taken precedence.",2,"Deployed- Side (door, seatback)",1,1,1,1,1,1,1,1,1,1
FARS,person,AIR_BAG,air_bag,Air Bag Deployed,This data element records air bag availability and deployment for this person as reported in the case material.,"This data element is designed to collect both air bag availability and deployment for each occupied seat position. Variation in the presentation of the source data on the State crash report forms and the selections coded on the police crash report may produce unlikely combinations or missing data. For example:    1. If the seat position does not have an air bag at the time of manufacture, but the       information on the police crash report indicates an air bag was available or deployed, the       information on the police crash report may have taken precedence.    2. If the seat position has an air bag installed at the time of manufacture and the police crash       report indicates there is no air bag available, then the police crash report information may       have taken precedence.",3,Deployed- Curtain (roof),1,1,1,1,1,1,1,1,1,1
FARS,person,AIR_BAG,air_bag,Air Bag Deployed,This data element records air bag availability and deployment for this person as reported in the case material.,"This data element is designed to collect both air bag availability and deployment for each occupied seat position. Variation in the presentation of the source data on the State crash report forms and the selections coded on the police crash report may produce unlikely combinations or missing data. For example:    1. If the seat position does not have an air bag at the time of manufacture, but the       information on the police crash report indicates an air bag was available or deployed, the       information on the police crash report may have taken precedence.    2. If the seat position has an air bag installed at the time of manufacture and the police crash       report indicates there is no air bag available, then the police crash report information may       have taken precedence.",7,"Deployed- Other (Knee, air belt, etc.)",1,1,1,1,1,1,1,1,1,1
FARS,person,AIR_BAG,air_bag,Air Bag Deployed,This data element records air bag availability and deployment for this person as reported in the case material.,"This data element is designed to collect both air bag availability and deployment for each occupied seat position. Variation in the presentation of the source data on the State crash report forms and the selections coded on the police crash report may produce unlikely combinations or missing data. For example:    1. If the seat position does not have an air bag at the time of manufacture, but the       information on the police crash report indicates an air bag was available or deployed, the       information on the police crash report may have taken precedence.    2. If the seat position has an air bag installed at the time of manufacture and the police crash       report indicates there is no air bag available, then the police crash report information may       have taken precedence.",8,Deployed- Combination,1,1,1,1,1,1,1,1,1,1
FARS,person,AIR_BAG,air_bag,Air Bag Deployed,This data element records air bag availability and deployment for this person as reported in the case material.,"This data element is designed to collect both air bag availability and deployment for each occupied seat position. Variation in the presentation of the source data on the State crash report forms and the selections coded on the police crash report may produce unlikely combinations or missing data. For example:    1. If the seat position does not have an air bag at the time of manufacture, but the       information on the police crash report indicates an air bag was available or deployed, the       information on the police crash report may have taken precedence.    2. If the seat position has an air bag installed at the time of manufacture and the police crash       report indicates there is no air bag available, then the police crash report information may       have taken precedence.",9,Deployment- Unknown Location,1,1,1,1,1,1,1,1,1,1
FARS,person,AIR_BAG,air_bag,Air Bag Deployed,This data element records air bag availability and deployment for this person as reported in the case material.,"This data element is designed to collect both air bag availability and deployment for each occupied seat position. Variation in the presentation of the source data on the State crash report forms and the selections coded on the police crash report may produce unlikely combinations or missing data. For example:    1. If the seat position does not have an air bag at the time of manufacture, but the       information on the police crash report indicates an air bag was available or deployed, the       information on the police crash report may have taken precedence.    2. If the seat position has an air bag installed at the time of manufacture and the police crash       report indicates there is no air bag available, then the police crash report information may       have taken precedence.",20,Not Deployed,1,1,1,1,1,1,1,1,1,1
FARS,person,AIR_BAG,air_bag,Air Bag Deployed,This data element records air bag availability and deployment for this person as reported in the case material.,"This data element is designed to collect both air bag availability and deployment for each occupied seat position. Variation in the presentation of the source data on the State crash report forms and the selections coded on the police crash report may produce unlikely combinations or missing data. For example:    1. If the seat position does not have an air bag at the time of manufacture, but the       information on the police crash report indicates an air bag was available or deployed, the       information on the police crash report may have taken precedence.    2. If the seat position has an air bag installed at the time of manufacture and the police crash       report indicates there is no air bag available, then the police crash report information may       have taken precedence.",28,Switched Off,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,person,AIR_BAG,air_bag,Air Bag Deployed,This data element records air bag availability and deployment for this person as reported in the case material.,"This data element is designed to collect both air bag availability and deployment for each occupied seat position. Variation in the presentation of the source data on the State crash report forms and the selections coded on the police crash report may produce unlikely combinations or missing data. For example:    1. If the seat position does not have an air bag at the time of manufacture, but the       information on the police crash report indicates an air bag was available or deployed, the       information on the police crash report may have taken precedence.    2. If the seat position has an air bag installed at the time of manufacture and the police crash       report indicates there is no air bag available, then the police crash report information may       have taken precedence.",97,Not a Motor Vehicle Occupant,1,1,1,1,1,1,1,1,1,1
FARS,person,AIR_BAG,air_bag,Air Bag Deployed,This data element records air bag availability and deployment for this person as reported in the case material.,"This data element is designed to collect both air bag availability and deployment for each occupied seat position. Variation in the presentation of the source data on the State crash report forms and the selections coded on the police crash report may produce unlikely combinations or missing data. For example:    1. If the seat position does not have an air bag at the time of manufacture, but the       information on the police crash report indicates an air bag was available or deployed, the       information on the police crash report may have taken precedence.    2. If the seat position has an air bag installed at the time of manufacture and the police crash       report indicates there is no air bag available, then the police crash report information may       have taken precedence.",98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,person,AIR_BAG,air_bag,Air Bag Deployed,This data element records air bag availability and deployment for this person as reported in the case material.,"This data element is designed to collect both air bag availability and deployment for each occupied seat position. Variation in the presentation of the source data on the State crash report forms and the selections coded on the police crash report may produce unlikely combinations or missing data. For example:    1. If the seat position does not have an air bag at the time of manufacture, but the       information on the police crash report indicates an air bag was available or deployed, the       information on the police crash report may have taken precedence.    2. If the seat position has an air bag installed at the time of manufacture and the police crash       report indicates there is no air bag available, then the police crash report information may       have taken precedence.",99,Deployment Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,EJECTION,ejection,Ejection,"This data element describes the ejection status and degree of ejection for this person, excluding motorcycle occupants.","In the mid 1970’s there were a large number of people coded as ejection unknown and a corresponding small number of people coded as not ejected. However, the totally ejected and partially ejected counts are the same magnitude as in later years. Starting in 2011 “Not Applicable” includes people not in motor vehicles (pedestrians, bicyclists, etc.)",0,Not Ejected,1,1,1,1,1,1,1,1,1,1
FARS,person,EJECTION,ejection,Ejection,"This data element describes the ejection status and degree of ejection for this person, excluding motorcycle occupants.","In the mid 1970’s there were a large number of people coded as ejection unknown and a corresponding small number of people coded as not ejected. However, the totally ejected and partially ejected counts are the same magnitude as in later years. Starting in 2011 “Not Applicable” includes people not in motor vehicles (pedestrians, bicyclists, etc.)",1,Totally Ejected,1,1,1,1,1,1,1,1,1,1
FARS,person,EJECTION,ejection,Ejection,"This data element describes the ejection status and degree of ejection for this person, excluding motorcycle occupants.","In the mid 1970’s there were a large number of people coded as ejection unknown and a corresponding small number of people coded as not ejected. However, the totally ejected and partially ejected counts are the same magnitude as in later years. Starting in 2011 “Not Applicable” includes people not in motor vehicles (pedestrians, bicyclists, etc.)",2,Partially Ejected,1,1,1,1,1,1,1,1,1,1
FARS,person,EJECTION,ejection,Ejection,"This data element describes the ejection status and degree of ejection for this person, excluding motorcycle occupants.","In the mid 1970’s there were a large number of people coded as ejection unknown and a corresponding small number of people coded as not ejected. However, the totally ejected and partially ejected counts are the same magnitude as in later years. Starting in 2011 “Not Applicable” includes people not in motor vehicles (pedestrians, bicyclists, etc.)",3,Ejected - Unknown Degree,1,1,1,1,1,1,1,1,1,1
FARS,person,EJECTION,ejection,Ejection,"This data element describes the ejection status and degree of ejection for this person, excluding motorcycle occupants.","In the mid 1970’s there were a large number of people coded as ejection unknown and a corresponding small number of people coded as not ejected. However, the totally ejected and partially ejected counts are the same magnitude as in later years. Starting in 2011 “Not Applicable” includes people not in motor vehicles (pedestrians, bicyclists, etc.)",7,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,person,EJECTION,ejection,Ejection,"This data element describes the ejection status and degree of ejection for this person, excluding motorcycle occupants.","In the mid 1970’s there were a large number of people coded as ejection unknown and a corresponding small number of people coded as not ejected. However, the totally ejected and partially ejected counts are the same magnitude as in later years. Starting in 2011 “Not Applicable” includes people not in motor vehicles (pedestrians, bicyclists, etc.)",8,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,person,EJECTION,ejection,Ejection,"This data element describes the ejection status and degree of ejection for this person, excluding motorcycle occupants.","In the mid 1970’s there were a large number of people coded as ejection unknown and a corresponding small number of people coded as not ejected. However, the totally ejected and partially ejected counts are the same magnitude as in later years. Starting in 2011 “Not Applicable” includes people not in motor vehicles (pedestrians, bicyclists, etc.)",9,Unknown if Ejected,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,EJ_PATH,ej_path,Ejection Path,This data element identifies the path by which this person was ejected from the vehicle.,NA,0,Not Ejected/Not Applicable,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,EJ_PATH,ej_path,Ejection Path,This data element identifies the path by which this person was ejected from the vehicle.,NA,1,Through Side Door Opening,1,1,1,1,1,1,1,1,1,1
FARS,person,EJ_PATH,ej_path,Ejection Path,This data element identifies the path by which this person was ejected from the vehicle.,NA,2,Through Side Window,1,1,1,1,1,1,1,1,1,1
FARS,person,EJ_PATH,ej_path,Ejection Path,This data element identifies the path by which this person was ejected from the vehicle.,NA,3,Through Windshield,1,1,1,1,1,1,1,1,1,1
FARS,person,EJ_PATH,ej_path,Ejection Path,This data element identifies the path by which this person was ejected from the vehicle.,NA,4,Through Back Window,1,1,1,1,1,1,1,1,1,1
FARS,person,EJ_PATH,ej_path,Ejection Path,This data element identifies the path by which this person was ejected from the vehicle.,NA,5,Through Back Door/Tailgate Opening,1,1,1,1,1,1,1,1,1,1
FARS,person,EJ_PATH,ej_path,Ejection Path,This data element identifies the path by which this person was ejected from the vehicle.,NA,6,"Through Roof Opening (sun-roof, convertible top down)",1,1,1,1,1,1,1,1,1,1
FARS,person,EJ_PATH,ej_path,Ejection Path,This data element identifies the path by which this person was ejected from the vehicle.,NA,7,Through roof (convertible top up),1,1,1,1,1,1,1,1,1,1
FARS,person,EJ_PATH,ej_path,Ejection Path,This data element identifies the path by which this person was ejected from the vehicle.,NA,8,"Other Path (e.g., back of pick-up truck)",1,1,1,1,1,1,1,1,1,1
FARS,person,EJ_PATH,ej_path,Ejection Path,This data element identifies the path by which this person was ejected from the vehicle.,NA,9,Unknown/Unknown Path,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,EXTRICAT,extricat,Extrication,This data element identifies if equipment was used to remove this person from the vehicle.,"In Massachusetts, if an occupant is not injured, data for Protection system use and ejection are not coded on the police crash report. From 1975 to 1976 the EXTRICAT and EJECTION data elements were combined in a single field. The data files were changed in 1977 to the current format. In 1975 and 1976 there are fewer people identified as not extricated than in later years. Both the count of extricated people and unknowns seem high for these years. From 1977 to 1981 there was not an edit check to prevent one coding an occupant as being both ejected and extricated. There are 69, 48, 83, 98, and 88 people coded as both totally ejected and extricated in the 1977, 1978, 1979, 1980, and 1981 respectively.",0,Not Extricated or Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,person,EXTRICAT,extricat,Extrication,This data element identifies if equipment was used to remove this person from the vehicle.,"In Massachusetts, if an occupant is not injured, data for Protection system use and ejection are not coded on the police crash report. From 1975 to 1976 the EXTRICAT and EJECTION data elements were combined in a single field. The data files were changed in 1977 to the current format. In 1975 and 1976 there are fewer people identified as not extricated than in later years. Both the count of extricated people and unknowns seem high for these years. From 1977 to 1981 there was not an edit check to prevent one coding an occupant as being both ejected and extricated. There are 69, 48, 83, 98, and 88 people coded as both totally ejected and extricated in the 1977, 1978, 1979, 1980, and 1981 respectively.",1,Extricated,1,1,1,1,1,1,1,1,1,1
FARS,person,EXTRICAT,extricat,Extrication,This data element identifies if equipment was used to remove this person from the vehicle.,"In Massachusetts, if an occupant is not injured, data for Protection system use and ejection are not coded on the police crash report. From 1975 to 1976 the EXTRICAT and EJECTION data elements were combined in a single field. The data files were changed in 1977 to the current format. In 1975 and 1976 there are fewer people identified as not extricated than in later years. Both the count of extricated people and unknowns seem high for these years. From 1977 to 1981 there was not an edit check to prevent one coding an occupant as being both ejected and extricated. There are 69, 48, 83, 98, and 88 people coded as both totally ejected and extricated in the 1977, 1978, 1979, 1980, and 1981 respectively.",9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,person,DRINKING,drinking,Police Reported Alcohol Involvement,This data element records whether alcohol was involved for this person and reflects the judgment of law enforcement.,"This data element does not indicate that alcohol was a cause of the crash. If a police crash report indicates that opened or unopened alcohol bottles were found in the vehicle, then this information does not by itself constitute involvement. Prior to 2019 the Data Element ID was P16/NM15. From 2019-2021 the Element Data ID was P16/NM16.",0,No (Alcohol Not Involved),1,1,1,1,1,1,1,1,1,1
FARS,person,DRINKING,drinking,Police Reported Alcohol Involvement,This data element records whether alcohol was involved for this person and reflects the judgment of law enforcement.,"This data element does not indicate that alcohol was a cause of the crash. If a police crash report indicates that opened or unopened alcohol bottles were found in the vehicle, then this information does not by itself constitute involvement. Prior to 2019 the Data Element ID was P16/NM15. From 2019-2021 the Element Data ID was P16/NM16.",1,Yes (Alcohol Involved),1,1,1,1,1,1,1,1,1,1
FARS,person,DRINKING,drinking,Police Reported Alcohol Involvement,This data element records whether alcohol was involved for this person and reflects the judgment of law enforcement.,"This data element does not indicate that alcohol was a cause of the crash. If a police crash report indicates that opened or unopened alcohol bottles were found in the vehicle, then this information does not by itself constitute involvement. Prior to 2019 the Data Element ID was P16/NM15. From 2019-2021 the Element Data ID was P16/NM16.",8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,person,DRINKING,drinking,Police Reported Alcohol Involvement,This data element records whether alcohol was involved for this person and reflects the judgment of law enforcement.,"This data element does not indicate that alcohol was a cause of the crash. If a police crash report indicates that opened or unopened alcohol bottles were found in the vehicle, then this information does not by itself constitute involvement. Prior to 2019 the Data Element ID was P16/NM15. From 2019-2021 the Element Data ID was P16/NM16.",9,Unknown (Police Reported),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,ALC_DET,alc_det,Method of Alcohol Determination by Police,NA,NA,1,"Evidential Test (breath, blood, urine)",1,1,1,1,1,1,1,1,NA,NA
FARS,person,ALC_DET,alc_det,Method of Alcohol Determination by Police,NA,NA,2,Preliminary Breath Test (PBT),1,1,1,1,1,1,1,1,NA,NA
FARS,person,ALC_DET,alc_det,Method of Alcohol Determination by Police,NA,NA,3,Behavioral,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,ALC_DET,alc_det,Method of Alcohol Determination by Police,NA,NA,4,Passive Alcohol Sensor (PAS),1,1,1,1,1,1,1,1,NA,NA
FARS,person,ALC_DET,alc_det,Method of Alcohol Determination by Police,NA,NA,5,Observed,1,1,1,1,1,1,1,1,NA,NA
FARS,person,ALC_DET,alc_det,Method of Alcohol Determination by Police,NA,NA,8,"Other (e.g., Saliva test)",1,1,1,1,1,1,1,1,NA,NA
FARS,person,ALC_DET,alc_det,Method of Alcohol Determination by Police,NA,NA,9,Not Reported,1,1,1,1,1,1,1,1,NA,NA
FARS,person,ALC_STATUS,alc_status,Alcohol Test- Status,This data element identifies whether an alcohol test was given to this person.,Prior to 2019 the Data Element ID was P18A/NM17A. From 2019-2021 the Data Element ID was P18A/NM18A.,0,Test Not Given,1,1,1,1,1,1,1,1,1,1
FARS,person,ALC_STATUS,alc_status,Alcohol Test- Status,This data element identifies whether an alcohol test was given to this person.,Prior to 2019 the Data Element ID was P18A/NM17A. From 2019-2021 the Data Element ID was P18A/NM18A.,1,Test Refused,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_STATUS,alc_status,Alcohol Test- Status,This data element identifies whether an alcohol test was given to this person.,Prior to 2019 the Data Element ID was P18A/NM17A. From 2019-2021 the Data Element ID was P18A/NM18A.,2,Test Given,1,1,1,1,1,1,1,1,1,1
FARS,person,ALC_STATUS,alc_status,Alcohol Test- Status,This data element identifies whether an alcohol test was given to this person.,Prior to 2019 the Data Element ID was P18A/NM17A. From 2019-2021 the Data Element ID was P18A/NM18A.,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,person,ALC_STATUS,alc_status,Alcohol Test- Status,This data element identifies whether an alcohol test was given to this person.,Prior to 2019 the Data Element ID was P18A/NM17A. From 2019-2021 the Data Element ID was P18A/NM18A.,9,UnKnown if Tested,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,0,Test Not Given,1,1,1,1,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,1,Blood,1,1,1,1,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,2,"Breathalyzer ""BAC""",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,3,Urine,1,1,1,1,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,4,Vitreous,1,1,1,1,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,5,Blood Plasma/Serum,1,1,1,1,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,6,Blood Clot,1,1,1,1,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,7,Liver,1,1,1,1,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,8,Other Test Type,1,1,1,1,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,10,Preliminary Breath Test (PBT),1,1,1,1,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,95,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,98,Unknown Test Type,1,1,1,1,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,99,Unknown if Tested,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,0,0.00 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,1,0.01 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,2,0.02 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,3,0.03 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,4,0.04 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,5,0.05 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,6,0.06 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,7,0.07 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,8,0.08 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,9,0.09 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,10,0.10 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,11,0.11 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,12,0.12 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,13,0.13 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,14,0.14 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,15,0.15 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,16,0.16 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,17,0.17 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,18,0.18 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,19,0.19 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,20,0.20 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,21,0.21 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,22,0.22 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,23,0.23 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,24,0.24 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,25,0.25 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,26,0.26 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,27,0.27 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,28,0.28 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,29,0.29 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,30,0.30 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,31,0.31 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,32,0.32 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,33,0.33 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,34,0.34 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,35,0.35 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,36,0.36 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,37,0.37 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,38,0.38 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,39,0.39 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,40,0.40 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,41,0.41 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,42,0.42 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,43,0.43 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,44,0.44 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,45,0.45 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,46,0.46 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,47,0.47 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,48,0.48 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,49,0.49 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,50,0.50 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,51,0.51 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,52,0.52 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,53,0.53 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,54,0.54 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,55,0.55 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,56,0.56 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,57,0.57 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,58,0.58 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,59,0.59 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,60,0.60 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,61,0.61 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,62,0.62 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,63,0.63 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,64,0.64 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,65,0.65 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,66,0.66 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,67,0.67 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,68,0.68 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,69,0.69 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,70,0.70 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,71,0.71 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,72,0.72 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,73,0.73 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,74,0.74 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,75,0.75 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,76,0.76 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,77,0.77 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,78,0.78 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,79,0.79 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,80,0.80 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,81,0.81 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,82,0.82 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,83,0.83 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,84,0.84 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,85,0.85 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,86,0.86 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,87,0.87 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,88,0.88 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,89,0.89 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,90,0.90 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,91,0.91 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,92,0.92 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,93,0.93 % BAC,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,94,0.94 % or Greater,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,95,Not Reported,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,96,Test Not Given,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,97,"AC Test Performed,Results Unknown",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,98,Positive Reading With No Actual Value,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,99,Unknown if tested,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,DRUGS,drugs,Police Reported Drug Involvement,This data element records whether drugs were involved for this person and reflects the judgment of law enforcement.,Prior to 2019 the Data Element ID was P19/NM18. From 2019-2021 the Data Element ID was P19/NM19.,0,No (drugs not involved),1,1,1,1,1,1,1,1,1,1
FARS,person,DRUGS,drugs,Police Reported Drug Involvement,This data element records whether drugs were involved for this person and reflects the judgment of law enforcement.,Prior to 2019 the Data Element ID was P19/NM18. From 2019-2021 the Data Element ID was P19/NM19.,1,Yes (drugs involved),1,1,1,1,1,1,1,1,1,1
FARS,person,DRUGS,drugs,Police Reported Drug Involvement,This data element records whether drugs were involved for this person and reflects the judgment of law enforcement.,Prior to 2019 the Data Element ID was P19/NM18. From 2019-2021 the Data Element ID was P19/NM19.,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,person,DRUGS,drugs,Police Reported Drug Involvement,This data element records whether drugs were involved for this person and reflects the judgment of law enforcement.,Prior to 2019 the Data Element ID was P19/NM18. From 2019-2021 the Data Element ID was P19/NM19.,9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUG_DET,drug_det,Method of Drug Determination by Police,This data element identifies the method by which the police made the determination as to whether drugs were involved for this person.,Prior to 2019 the Data Element ID was P20/NM19.,1,"Evidential Test (Blood, Urine)",1,1,1,1,1,1,1,1,NA,NA
FARS,person,DRUG_DET,drug_det,Method of Drug Determination by Police,This data element identifies the method by which the police made the determination as to whether drugs were involved for this person.,Prior to 2019 the Data Element ID was P20/NM19.,2,Drug Recognition Technician (DRT) determination,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,DRUG_DET,drug_det,Method of Drug Determination by Police,This data element identifies the method by which the police made the determination as to whether drugs were involved for this person.,Prior to 2019 the Data Element ID was P20/NM19.,3,Behavioral,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,DRUG_DET,drug_det,Method of Drug Determination by Police,This data element identifies the method by which the police made the determination as to whether drugs were involved for this person.,Prior to 2019 the Data Element ID was P20/NM19.,7,Other,1,1,1,1,1,1,1,1,NA,NA
FARS,person,DRUG_DET,drug_det,Method of Drug Determination by Police,This data element identifies the method by which the police made the determination as to whether drugs were involved for this person.,Prior to 2019 the Data Element ID was P20/NM19.,8,Not Reported,1,1,1,1,1,1,1,1,NA,NA
FARS,person,DSTATUS,dstatus,Drug Test -Status,This data element identifies whether a drug test was given to this person.,Prior to 2019 the Data Element ID was P21A/NM20A. From 2019-2021 the Data Element ID was P21A/NM21A.,0,Test Not Given,1,1,1,1,1,1,1,1,1,1
FARS,person,DSTATUS,dstatus,Drug Test -Status,This data element identifies whether a drug test was given to this person.,Prior to 2019 the Data Element ID was P21A/NM20A. From 2019-2021 the Data Element ID was P21A/NM21A.,1,Test Refused,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,person,DSTATUS,dstatus,Drug Test -Status,This data element identifies whether a drug test was given to this person.,Prior to 2019 the Data Element ID was P21A/NM20A. From 2019-2021 the Data Element ID was P21A/NM21A.,2,Test Given,1,1,1,1,1,1,1,1,1,1
FARS,person,DSTATUS,dstatus,Drug Test -Status,This data element identifies whether a drug test was given to this person.,Prior to 2019 the Data Element ID was P21A/NM20A. From 2019-2021 the Data Element ID was P21A/NM21A.,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,person,DSTATUS,dstatus,Drug Test -Status,This data element identifies whether a drug test was given to this person.,Prior to 2019 the Data Element ID was P21A/NM20A. From 2019-2021 the Data Element ID was P21A/NM21A.,9,Unknown if Tested,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST1,drugtst1,Drug Test -Type (1),NA,NA,0,Test Not Given,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST1,drugtst1,Drug Test -Type (1),NA,NA,1,Blood,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST1,drugtst1,Drug Test -Type (1),NA,NA,2,Urine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST1,drugtst1,Drug Test -Type (1),NA,NA,3,Both: Blood and Urine Tests,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST1,drugtst1,Drug Test -Type (1),NA,NA,6,Not Reported,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST1,drugtst1,Drug Test -Type (1),NA,NA,7,Unknown Test Type,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST1,drugtst1,Drug Test -Type (1),NA,NA,8,Other Test Type,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST1,drugtst1,Drug Test -Type (1),NA,NA,9,Unknown if Tested,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST2,drugtst2,Drug Test -Type (2),NA,NA,0,Test Not Given,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST2,drugtst2,Drug Test -Type (2),NA,NA,1,Blood,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST2,drugtst2,Drug Test -Type (2),NA,NA,2,Urine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST2,drugtst2,Drug Test -Type (2),NA,NA,3,Both: Blood and Urine Tests,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST2,drugtst2,Drug Test -Type (2),NA,NA,6,Not Reported,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST2,drugtst2,Drug Test -Type (2),NA,NA,7,Unknown Test Type,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST2,drugtst2,Drug Test -Type (2),NA,NA,8,Other Test Type,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST2,drugtst2,Drug Test -Type (2),NA,NA,9,Unknown if Tested,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST3,drugtst3,Drug Test -Type (3),NA,NA,0,Test Not Given,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST3,drugtst3,Drug Test -Type (3),NA,NA,1,Blood,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST3,drugtst3,Drug Test -Type (3),NA,NA,2,Urine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST3,drugtst3,Drug Test -Type (3),NA,NA,3,Both: Blood and Urine Tests,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST3,drugtst3,Drug Test -Type (3),NA,NA,6,Not Reported,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST3,drugtst3,Drug Test -Type (3),NA,NA,7,Unknown Test Type,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST3,drugtst3,Drug Test -Type (3),NA,NA,8,Other Test Type,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGTST3,drugtst3,Drug Test -Type (3),NA,NA,9,Unknown if Tested,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",0,Test Not Given,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",1,"Tested, No Drugs Found/Negative",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",95,Not Reported,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",100,Acetaminophen + Codeine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",101,Acetorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",102,Acetyl-alpha-methylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",103,Acetyldihydrocodeine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",104,ACETYLMETHADOL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",105,Alfentanil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",106,Allylprodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",107,Alpha-methylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",108,Alphamethythiofentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",109,Alpha-meprodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",110,Alphamethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",111,ALPHAPRODINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",112,ANILERIDINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",113,APC + CODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",114,ASPRIN + CODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",115,Benzethidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",117,Benzylmorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",118,Beta-hydroxyfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",119,Betacetylmethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",120,Beta-meprodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",121,Betamethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",122,Betaprodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",123,Bezitramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",124,Buprenorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",125,Carfentanil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",126,Clonitazene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",127,Codeine methylbromide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",128,CODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",129,Cyprenorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",130,Desomorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",131,Dextromoramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",133,Diampromide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",134,Diethylthiambutene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",135,Difenoxin,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",136,DIHYDROCODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",137,Dihydromorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",138,Dimenoxadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",139,Dimepheptanol (Racemethadol),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",140,Dimethylthiambutene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",141,Dioxaphetyl Butyrate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",142,Diphenoxylate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",143,Dipipanone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",144,Diprenorphine Hydrochloride,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",146,Ethylmethylthiambutene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",147,ETHYLMORPHINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",148,Etonitazene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",149,ETORPHINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",150,Extoxeridine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",151,FENTANYL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",152,FIORINAL + CODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",153,Furethidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",154,Heroin (Diacetylmorphine),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",155,HYDROCODONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",156,Hydromorphinol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",157,HYDROMORPHONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",158,Hydroxypethidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",159,Isomethadone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",160,Ketobemidone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",161,Levomoramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",162,Levophenacylmorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",163,Levormethorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",164,LEVORPHANOL TARTRATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",165,MEPERIDINE (Pethidine),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",166,Metazocine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",167,METHADONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",168,Methyldesorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",169,Methyldihydromorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",170,Methylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",171,Methylphenylpropionoxypiperidine (MPPP),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",172,Metopon,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",173,Moramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",174,Morpheridine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",175,Morphine methylsulfonate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",176,Morphine methylbromide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",177,MORPHINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",178,Myrophine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",179,NALORPHINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",180,Nicocodeine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",181,Nicomorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",182,Noracymethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",183,Norlevorphanol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",184,Normethadone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",185,Normorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",186,Norpipanone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",187,OPIUM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",188,Oxymorphone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",189,OXYCODONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",190,Parafluorofentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",191,PAREGORIC,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",192,PAREPECTOLIN,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",193,PENTAZOCINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",195,Phenadoxone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",196,Phenampromide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",197,Phenanthrine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",198,Phenazocine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",199,Phenomorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",200,Phenoperidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",202,Pholcodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",203,Piminodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",204,Piritramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",205,Proheptazine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",206,Properidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",207,Propiram,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",208,"Propoxyphene (Dextropropoxyphene, bulk (non-dosage forms))",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",209,Racemethorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",210,Racemoramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",211,Racemorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",212,Sufentanil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",213,Thebacon,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",214,Thebaine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",215,Thiofentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",216,Tilidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",217,Trimeperidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",218,Butorphanol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",220,Alphacetylmethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",221,Beta-Hydroxy-3-methylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",222,Codeine & isoquinoline,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",223,Codeine-N-oxide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",224,Dextropropoxyphene (dosage forms),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",225,Difenenoxin,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",226,Dihydroetrophine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",227,Diprenorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",228,Levo-alphacetylmethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",229,Levorphanol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",230,Methylthiofentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",231,Morphine-N-oxide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",232,Opium extract,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",233,Opium fluid extract,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",234,Opium Poppy,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",235,Opium Tincture,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",236,Phenylethyl-phenyl-acetoxypiperidine (PEPAP),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",237,Poppy Straw,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",238,Poppy Straw Concentrate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",239,Remifentanil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",240,Codeine combination product 90 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",241,Codeine preparations - 200 mg/100 ml or 100 gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",242,Difenoxin 1 mg/25ug AtSO4/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",243,Difenoxin preparations - 0.5 mg/25 ug AtSO4/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",244,Dihydrocodeine combination product 90 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",245,Dihydrocodeine preparations 10 mg/100 ml or 100 gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",246,Diphenoxylate preparations 2.5 mg/25 ug AtSO4,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",247,Ethylmorphine combination product 15 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",248,Ethylmorphine preparations 100 mg/100 ml or 100 gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",249,Hydrocodone & isoquinoline alkaloid<15 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",250,Hydrocodone combination product<15 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",251,Meperidine intermediate-A,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",252,Meperidine intermediate-B,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",253,Meperidine intermediate-C,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",254,Methadone intermediate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",255,Morphine combination product/50 mg/100 ml or gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",256,Opium combination product 25 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",257,Opium preparations - 100 mg/100 ml or/100 gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",258,"Opium, granulated",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",259,"Opium, powdered",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",260,Oripavine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",295,"""Narcotics, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",300,ALPRAZOLAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",301,AMOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",302,Barbital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",303,BARBITURATES,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",304,BENZODIAZEPINES,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",305,Benzylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",306,Bromazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",307,BUTABARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",308,Butalbital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",309,Camazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",310,CARBAMATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",311,Chloral betaine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",312,Chloral Hydrate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",313,CHLORDIAZEPROXIDE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",314,Chlorhexadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",315,Clobazam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",316,Clonazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",317,CLORAZEPATE DIPOTASSIUM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",318,Clotiazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",319,Cloxazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",320,Delorazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",321,DIAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",322,Estazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",323,ETHCHLORVYNOL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",324,Ethinamate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",325,Ethyl Ioflazepate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",326,Fiorinal,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",327,Fludiazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",328,Flunitrazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",330,GLUTETHIMIDE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",331,HALAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",332,Haloxazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",333,HEXOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",334,Hydroxyzine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",335,Ketazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",336,Loprazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",337,LORAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",338,Lormetazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",339,Mebutamate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",340,Mecloqualone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",341,Medazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",342,MEPHOBARBITAL (Methylphenobarbital),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",343,MEPROBAMATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",344,METHAQUALONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",345,METHARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",346,Methohexital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",347,METHYPRYLON,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",348,Midazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",349,Nimetazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",350,Nitrazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",351,Nordiazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",352,OXAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",353,Oxazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",354,Paraldehyde,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",355,PENTOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",356,Petrichloral,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",357,Phencyclohexylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",358,PHENOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",359,Pinazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",360,PRAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",361,Quazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",362,SECOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",363,Sulfondiethylmethane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",364,Sulfonethylmethane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",365,Sulfonmethane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",366,TALBUTAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",367,TEMAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",368,Tetrazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",369,Thenylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",370,Thiamylal,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",371,Thiopental (Pentothal),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",372,Tiletamine/Zolazepam (Telazol),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",373,TRAIZOLAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",374,TYBAMATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",376,Carisoprodol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",377,Gamma Hydroxybutryate (GHB),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",378,Amobarbital & non-controlled active ingred.,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",379,Aprobarbital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",380,Barbituric Acid Derivative,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",383,Dexfenfluramine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",384,Flurazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",385,Sibutramine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",386,Zaleplon,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",387,Zolpidem,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",388,Amobarbital suppository dosage form,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",389,Butobarbital (butethal),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",390,Embutramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",391,Gamma Hydroxybutyric Acid preparations,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",393,Pentobarbital & noncontrolled active ingred.,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",394,Pentobarbital suppository dosage form,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",395,"""Depressants, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",396,Pregabalin,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",397,Secobarbital & noncontrolled active ingred.,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",398,Secobarbital suppository dosage form,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",399,Zopiclone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",400,AMPHETAMINE SULFATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",401,AMPHETAMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",402,BENZOYLECGONINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",403,BENZPHETAMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",404,Cathine (Norpseudoephedrine),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",405,Chlorphentermine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",406,Clortermine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",407,COCAINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",408,DEXTROAMPHETAMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",409,DIETHYLPROPION,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",410,Ecgonine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",411,Fencamfamin,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",412,FENETHYLLINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",413,Fenfluramine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",414,Fenproporex,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",415,MAZINDOL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",416,Menfenorex,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",417,METHAMPHETAMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",418,METHYLPHENIDATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",419,N-Ethylamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",420,PEMOLINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",421,PHENDIMETRAZINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",422,PHENMETRAZINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",423,PHENTERMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",424,Pipradrol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",425,Propylhexedrine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",426,Pyrovalerone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",427,SPA,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",428,Aminorex,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",429,Cathinone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",430,Coca Leaves,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",431,Dicholoralphenazone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",432,Methcathinone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",433,Modafinil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",434,Vinbarbital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",435,Methylone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",436,Lisdexamfetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",437,Methoxy-Methylenedioxyamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",438,"N, N-Dimethylamphetamine (Dimethylamphetamine)",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",439,N-Benzylpiperazine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",440,Stimulant compounds previously excepted,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",495,"""Stimulants, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",500,AMPHETAMINE VARIANTS,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",501,BUFOTENINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",503,Diethyltryptamine (DET),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",504,Dimethoxyamphetamine (DMA),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",505,Dimethyltryptamine(DMT),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",507,Dronabinol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",508,N-Ethyl-3-piperidyl benzilate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",509,IBOGAINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",511,LYSERGIC ACID,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",512,MESCALINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",513,Methylenedioxymethamphetamine (MDMA),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",514,Methoxyamphetamine (PMA),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",515,Methylenedioxyamphetamine (MDA),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",516,Nabilone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",517,PEYOTE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",518,Phenylacetone (P2P),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",519,PSILOCYBIN,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",520,PSILOCYN,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",521,Trimethoxy amphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",522,Ketamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",523,Alpha_Ethyltryptamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",524,Bromo-dimethoxyamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",525,Bromo-dimethoxyphenethylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",527,Lysergic Acid Amide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",528,Lysergic Acid Diethylamide (LSD),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",529,Methylaminorex,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",530,Methyl-dimethoxyamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",531,Methylenedioxy-N-ethylamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",532,Dimethylamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",533,N-Ethyl-1-phenylcyclohexylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",534,Alpha-methyltryptamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",535,Dimethoxyethylamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",536,Dimethoxy-(n)-propylthiophenethylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",537,Methoxy-NN-diisopropyltryptamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",538,N-Hydroxymethylenedioxy-amphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",539,N-Methylpiperidyl benzilate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",595,"""Hallucinogens, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",600,DELTA 9,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",601,HASHISH OIL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",602,HASHISH,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",603,MARIJUANA/Marihuana,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",604,MARINOL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",605,Tetrahydrocannabinols (THC),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",695,"""Cannabinoid, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",700,Ethylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",701,Parahexyl (Synhexyl),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",702,PHENCYCLIDINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",703,PHENCYCLIDINE ANALOGS,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",704,phenylcyclohexylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",705,Piperidinocyclohexane-carbonitrile (PCC),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",706,"""Pyrrolidine (PCPy,PHP,TCPy)""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",707,Thiophend,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",708,Thienylcyclohexylpiperidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",709,Phenylcyclohexyl-Pyrrolidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",710,Thienyl Cyclohexyl Pyrrolidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",795,"""PCP, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",800,Boldenone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",801,Chlorotestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",803,Dehydrochlomethyltestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",804,Dihydrotesterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",805,Drostanolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",806,Ethylestrenol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",807,Fluoxymesterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",808,Formebulone (Formebolone),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",809,Mesterolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",810,Methandienone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",811,Methandranone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",812,Methandriol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",813,Methandrostenolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",814,Methenolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",815,Methyltestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",816,Mibolerone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",817,Nandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",818,Norethandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",819,Oxandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",820,Oxymesterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",821,Oxymetholone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",822,Stanolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",823,Stanozolol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",824,Testolactone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",825,Testosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",826,Trenbolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",827,Clostebol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",828,"Alpha, Beta-dihydroxy-alpha-androstane",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",829,Alpha-methyl-alpha-beta-dihydroxy-alpha-androstane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",830,Alpha-methyl-beta-beta-dihydroxy-alpha-androstane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",831,Alpha-methyl-beta-beta-dihydroxy-androstene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",832,Alpha-methyl-delta 1-dihydrotestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",833,Alpha-methyl-hydroxynandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",834,Androstanedione,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",835,Androstenediol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",836,Androstenedione,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",837,"Beta, beta-dihydroxy-alpha-androstane",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",838,Bolasterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",839,Calusterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",840,Delta 1-dihydrotestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",841,Furazabol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",842,Hydroxy-Nortestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",843,Hydroxytestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",844,Mestanolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",845,Methyldienolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",846,Methyltrienolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",847,Norandrostenediol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",848,Norandrostenedione,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",849,Norbolethone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",850,Norclostebol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",851,Normethandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",852,Stenbolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",853,Tetrahydrogestrinone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",895,"Anabolic Steroid, Type Unknown",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",900,Volatile Solvents (toluene),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",901,Plastic Cement (airplane glue),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",902,Paint and Paint Removers,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",903,"""Petroleum Products (gasoline, kerosene)""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",904,Lacquer Thinners,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",920,Anesthetic Gases,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",921,Amyl Nitrite,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",923,Butly Nitrite,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",924,Nitrous Oxide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",925,Ether,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",926,Chloroform,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",940,Aerosols (hydrocarbon),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",941,Hair spray,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",942,Insecticides,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",943,Glass Chillers,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",944,Frying Pan Lubricants,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",995,"""Inhalants, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",996,Other Drug,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",997,"Test For Drug, Results Unknown",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",998,"Tested For Drugs, Drugs Found, Type unknown/Positive",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES1,drugres1,Drug Test- Result (1),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",999,Unknown if Tested,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",0,Test Not Given,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",1,"Tested, No Drugs Found/Negative",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",95,Not Reported,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",100,Acetaminophen + Codeine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",101,Acetorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",102,Acetyl-alpha-methylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",103,Acetyldihydrocodeine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",104,ACETYLMETHADOL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",105,Alfentanil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",106,Allylprodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",107,Alpha-methylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",108,Alphamethythiofentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",109,Alpha-meprodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",110,Alphamethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",111,ALPHAPRODINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",112,ANILERIDINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",113,APC + CODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",114,ASPRIN + CODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",115,Benzethidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",117,Benzylmorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",118,Beta-hydroxyfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",119,Betacetylmethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",120,Beta-meprodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",121,Betamethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",122,Betaprodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",123,Bezitramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",124,Buprenorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",125,Carfentanil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",126,Clonitazene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",127,Codeine methylbromide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",128,CODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",129,Cyprenorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",130,Desomorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",131,Dextromoramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",133,Diampromide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",134,Diethylthiambutene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",135,Difenoxin,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",136,DIHYDROCODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",137,Dihydromorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",138,Dimenoxadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",139,Dimepheptanol (Racemethadol),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",140,Dimethylthiambutene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",141,Dioxaphetyl Butyrate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",142,Diphenoxylate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",143,Dipipanone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",144,Diprenorphine Hydrochloride,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",146,Ethylmethylthiambutene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",147,ETHYLMORPHINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",148,Etonitazene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",149,ETORPHINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",150,Extoxeridine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",151,FENTANYL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",152,FIORINAL + CODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",153,Furethidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",154,Heroin (Diacetylmorphine),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",155,HYDROCODONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",156,Hydromorphinol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",157,HYDROMORPHONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",158,Hydroxypethidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",159,Isomethadone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",160,Ketobemidone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",161,Levomoramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",162,Levophenacylmorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",163,Levormethorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",164,LEVORPHANOL TARTRATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",165,MEPERIDINE (Pethidine),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",166,Metazocine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",167,METHADONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",168,Methyldesorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",169,Methyldihydromorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",170,Methylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",171,Methylphenylpropionoxypiperidine (MPPP),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",172,Metopon,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",173,Moramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",174,Morpheridine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",175,Morphine methylsulfonate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",176,Morphine methylbromide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",177,MORPHINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",178,Myrophine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",179,NALORPHINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",180,Nicocodeine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",181,Nicomorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",182,Noracymethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",183,Norlevorphanol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",184,Normethadone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",185,Normorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",186,Norpipanone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",187,OPIUM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",188,Oxymorphone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",189,OXYCODONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",190,Parafluorofentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",191,PAREGORIC,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",192,PAREPECTOLIN,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",193,PENTAZOCINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",195,Phenadoxone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",196,Phenampromide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",197,Phenanthrine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",198,Phenazocine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",199,Phenomorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",200,Phenoperidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",202,Pholcodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",203,Piminodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",204,Piritramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",205,Proheptazine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",206,Properidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",207,Propiram,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",208,"Propoxyphene (Dextropropoxyphene, bulk (non-dosage forms))",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",209,Racemethorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",210,Racemoramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",211,Racemorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",212,Sufentanil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",213,Thebacon,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",214,Thebaine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",215,Thiofentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",216,Tilidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",217,Trimeperidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",218,Butorphanol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",220,Alphacetylmethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",221,Beta-Hydroxy-3-methylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",222,Codeine & isoquinoline,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",223,Codeine-N-oxide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",224,Dextropropoxyphene (dosage forms),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",225,Difenenoxin,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",226,Dihydroetrophine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",227,Diprenorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",228,Levo-alphacetylmethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",229,Levorphanol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",230,Methylthiofentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",231,Morphine-N-oxide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",232,Opium extract,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",233,Opium fluid extract,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",234,Opium Poppy,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",235,Opium Tincture,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",236,Phenylethyl-phenyl-acetoxypiperidine (PEPAP),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",237,Poppy Straw,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",238,Poppy Straw Concentrate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",239,Remifentanil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",240,Codeine combination product 90 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",241,Codeine preparations - 200 mg/100 ml or 100 gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",242,Difenoxin 1 mg/25ug AtSO4/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",243,Difenoxin preparations - 0.5 mg/25 ug AtSO4/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",244,Dihydrocodeine combination product 90 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",245,Dihydrocodeine preparations 10 mg/100 ml or 100 gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",246,Diphenoxylate preparations 2.5 mg/25 ug AtSO4,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",247,Ethylmorphine combination product 15 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",248,Ethylmorphine preparations 100 mg/100 ml or 100 gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",249,Hydrocodone & isoquinoline alkaloid<15 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",250,Hydrocodone combination product<15 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",251,Meperidine intermediate-A,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",252,Meperidine intermediate-B,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",253,Meperidine intermediate-C,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",254,Methadone intermediate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",255,Morphine combination product/50 mg/100 ml or gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",256,Opium combination product 25 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",257,Opium preparations - 100 mg/100 ml or/100 gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",258,"Opium, granulated",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",259,"Opium, powdered",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",260,Oripavine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",295,"""Narcotics, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",300,ALPRAZOLAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",301,AMOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",302,Barbital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",303,BARBITURATES,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",304,BENZODIAZEPINES,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",305,Benzylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",306,Bromazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",307,BUTABARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",308,Butalbital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",309,Camazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",310,CARBAMATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",311,Chloral betaine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",312,Chloral Hydrate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",313,CHLORDIAZEPROXIDE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",314,Chlorhexadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",315,Clobazam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",316,Clonazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",317,CLORAZEPATE DIPOTASSIUM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",318,Clotiazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",319,Cloxazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",320,Delorazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",321,DIAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",322,Estazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",323,ETHCHLORVYNOL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",324,Ethinamate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",325,Ethyl Ioflazepate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",326,Fiorinal,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",327,Fludiazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",328,Flunitrazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",330,GLUTETHIMIDE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",331,HALAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",332,Haloxazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",333,HEXOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",334,Hydroxyzine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",335,Ketazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",336,Loprazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",337,LORAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",338,Lormetazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",339,Mebutamate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",340,Mecloqualone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",341,Medazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",342,MEPHOBARBITAL (Methylphenobarbital),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",343,MEPROBAMATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",344,METHAQUALONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",345,METHARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",346,Methohexital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",347,METHYPRYLON,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",348,Midazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",349,Nimetazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",350,Nitrazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",351,Nordiazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",352,OXAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",353,Oxazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",354,Paraldehyde,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",355,PENTOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",356,Petrichloral,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",357,Phencyclohexylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",358,PHENOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",359,Pinazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",360,PRAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",361,Quazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",362,SECOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",363,Sulfondiethylmethane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",364,Sulfonethylmethane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",365,Sulfonmethane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",366,TALBUTAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",367,TEMAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",368,Tetrazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",369,Thenylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",370,Thiamylal,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",371,Thiopental (Pentothal),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",372,Tiletamine/Zolazepam (Telazol),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",373,TRAIZOLAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",374,TYBAMATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",376,Carisoprodol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",377,Gamma Hydroxybutryate (GHB),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",378,Amobarbital & non-controlled active ingred.,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",379,Aprobarbital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",380,Barbituric Acid Derivative,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",383,Dexfenfluramine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",384,Flurazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",385,Sibutramine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",386,Zaleplon,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",387,Zolpidem,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",388,Amobarbital suppository dosage form,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",389,Butobarbital (butethal),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",390,Embutramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",391,Gamma Hydroxybutyric Acid preparations,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",393,Pentobarbital & noncontrolled active ingred.,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",394,Pentobarbital suppository dosage form,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",395,"""Depressants, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",396,Pregabalin,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",397,Secobarbital & noncontrolled active ingred.,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",398,Secobarbital suppository dosage form,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",399,Zopiclone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",400,AMPHETAMINE SULFATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",401,AMPHETAMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",402,BENZOYLECGONINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",403,BENZPHETAMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",404,Cathine (Norpseudoephedrine),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",405,Chlorphentermine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",406,Clortermine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",407,COCAINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",408,DEXTROAMPHETAMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",409,DIETHYLPROPION,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",410,Ecgonine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",411,Fencamfamin,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",412,FENETHYLLINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",413,Fenfluramine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",414,Fenproporex,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",415,MAZINDOL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",416,Menfenorex,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",417,METHAMPHETAMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",418,METHYLPHENIDATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",419,N-Ethylamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",420,PEMOLINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",421,PHENDIMETRAZINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",422,PHENMETRAZINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",423,PHENTERMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",424,Pipradrol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",425,Propylhexedrine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",426,Pyrovalerone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",427,SPA,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",428,Aminorex,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",429,Cathinone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",430,Coca Leaves,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",431,Dicholoralphenazone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",432,Methcathinone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",433,Modafinil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",434,Vinbarbital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",435,Methylone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",436,Lisdexamfetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",437,Methoxy-Methylenedioxyamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",438,"N, N-Dimethylamphetamine (Dimethylamphetamine)",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",439,N-Benzylpiperazine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",440,Stimulant compounds previously excepted,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",495,"""Stimulants, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",500,AMPHETAMINE VARIANTS,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",501,BUFOTENINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",503,Diethyltryptamine (DET),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",504,Dimethoxyamphetamine (DMA),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",505,Dimethyltryptamine(DMT),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",507,Dronabinol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",508,N-Ethyl-3-piperidyl benzilate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",509,IBOGAINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",511,LYSERGIC ACID,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",512,MESCALINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",513,Methylenedioxymethamphetamine (MDMA),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",514,Methoxyamphetamine (PMA),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",515,Methylenedioxyamphetamine (MDA),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",516,Nabilone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",517,PEYOTE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",518,Phenylacetone (P2P),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",519,PSILOCYBIN,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",520,PSILOCYN,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",521,Trimethoxy amphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",522,Ketamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",523,Alpha_Ethyltryptamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",524,Bromo-dimethoxyamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",525,Bromo-dimethoxyphenethylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",527,Lysergic Acid Amide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",528,Lysergic Acid Diethylamide (LSD),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",529,Methylaminorex,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",530,Methyl-dimethoxyamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",531,Methylenedioxy-N-ethylamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",532,Dimethylamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",533,N-Ethyl-1-phenylcyclohexylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",534,Alpha-methyltryptamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",535,Dimethoxyethylamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",536,Dimethoxy-(n)-propylthiophenethylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",537,Methoxy-NN-diisopropyltryptamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",538,N-Hydroxymethylenedioxy-amphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",539,N-Methylpiperidyl benzilate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",595,"""Hallucinogens, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",600,DELTA 9,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",601,HASHISH OIL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",602,HASHISH,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",603,MARIJUANA/Marihuana,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",604,MARINOL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",605,Tetrahydrocannabinols (THC),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",695,"""Cannabinoid, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",700,Ethylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",701,Parahexyl (Synhexyl),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",702,PHENCYCLIDINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",703,PHENCYCLIDINE ANALOGS,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",704,phenylcyclohexylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",705,Piperidinocyclohexane-carbonitrile (PCC),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",706,"""Pyrrolidine (PCPy,PHP,TCPy)""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",707,Thiophend,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",708,Thienylcyclohexylpiperidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",709,Phenylcyclohexyl-Pyrrolidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",710,Thienyl Cyclohexyl Pyrrolidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",795,"""PCP, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",800,Boldenone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",801,Chlorotestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",803,Dehydrochlomethyltestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",804,Dihydrotesterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",805,Drostanolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",806,Ethylestrenol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",807,Fluoxymesterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",808,Formebulone (Formebolone),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",809,Mesterolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",810,Methandienone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",811,Methandranone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",812,Methandriol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",813,Methandrostenolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",814,Methenolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",815,Methyltestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",816,Mibolerone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",817,Nandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",818,Norethandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",819,Oxandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",820,Oxymesterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",821,Oxymetholone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",822,Stanolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",823,Stanozolol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",824,Testolactone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",825,Testosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",826,Trenbolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",827,Clostebol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",828,"Alpha, Beta-dihydroxy-alpha-androstane",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",829,Alpha-methyl-alpha-beta-dihydroxy-alpha-androstane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",830,Alpha-methyl-beta-beta-dihydroxy-alpha-androstane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",831,Alpha-methyl-beta-beta-dihydroxy-androstene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",832,Alpha-methyl-delta 1-dihydrotestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",833,Alpha-methyl-hydroxynandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",834,Androstanedione,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",835,Androstenediol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",836,Androstenedione,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",837,"Beta, beta-dihydroxy-alpha-androstane",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",838,Bolasterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",839,Calusterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",840,Delta 1-dihydrotestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",841,Furazabol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",842,Hydroxy-Nortestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",843,Hydroxytestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",844,Mestanolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",845,Methyldienolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",846,Methyltrienolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",847,Norandrostenediol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",848,Norandrostenedione,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",849,Norbolethone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",850,Norclostebol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",851,Normethandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",852,Stenbolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",853,Tetrahydrogestrinone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",895,"Anabolic Steroid, Type Unknown",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",900,Volatile Solvents (toluene),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",901,Plastic Cement (airplane glue),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",902,Paint and Paint Removers,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",903,"""Petroleum Products (gasoline, kerosene)""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",904,Lacquer Thinners,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",920,Anesthetic Gases,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",921,Amyl Nitrite,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",923,Butly Nitrite,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",924,Nitrous Oxide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",925,Ether,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",926,Chloroform,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",940,Aerosols (hydrocarbon),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",941,Hair spray,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",942,Insecticides,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",943,Glass Chillers,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",944,Frying Pan Lubricants,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",995,"""Inhalants, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",996,Other Drug,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",997,"Test For Drug, Results Unknown",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",998,"Tested For Drugs, Drugs Found, Type unknown/Positive",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES2,drugres2,Drug Test- Result (2),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",999,Unknown if Tested,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",0,Test Not Given,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",1,"Tested, No Drugs Found/Negative",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",95,Not Reported,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",100,Acetaminophen + Codeine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",101,Acetorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",102,Acetyl-alpha-methylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",103,Acetyldihydrocodeine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",104,ACETYLMETHADOL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",105,Alfentanil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",106,Allylprodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",107,Alpha-methylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",108,Alphamethythiofentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",109,Alpha-meprodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",110,Alphamethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",111,ALPHAPRODINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",112,ANILERIDINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",113,APC + CODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",114,ASPRIN + CODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",115,Benzethidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",117,Benzylmorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",118,Beta-hydroxyfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",119,Betacetylmethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",120,Beta-meprodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",121,Betamethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",122,Betaprodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",123,Bezitramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",124,Buprenorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",125,Carfentanil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",126,Clonitazene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",127,Codeine methylbromide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",128,CODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",129,Cyprenorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",130,Desomorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",131,Dextromoramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",133,Diampromide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",134,Diethylthiambutene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",135,Difenoxin,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",136,DIHYDROCODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",137,Dihydromorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",138,Dimenoxadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",139,Dimepheptanol (Racemethadol),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",140,Dimethylthiambutene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",141,Dioxaphetyl Butyrate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",142,Diphenoxylate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",143,Dipipanone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",144,Diprenorphine Hydrochloride,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",146,Ethylmethylthiambutene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",147,ETHYLMORPHINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",148,Etonitazene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",149,ETORPHINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",150,Extoxeridine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",151,FENTANYL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",152,FIORINAL + CODEINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",153,Furethidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",154,Heroin (Diacetylmorphine),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",155,HYDROCODONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",156,Hydromorphinol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",157,HYDROMORPHONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",158,Hydroxypethidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",159,Isomethadone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",160,Ketobemidone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",161,Levomoramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",162,Levophenacylmorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",163,Levormethorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",164,LEVORPHANOL TARTRATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",165,MEPERIDINE (Pethidine),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",166,Metazocine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",167,METHADONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",168,Methyldesorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",169,Methyldihydromorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",170,Methylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",171,Methylphenylpropionoxypiperidine (MPPP),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",172,Metopon,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",173,Moramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",174,Morpheridine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",175,Morphine methylsulfonate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",176,Morphine methylbromide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",177,MORPHINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",178,Myrophine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",179,NALORPHINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",180,Nicocodeine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",181,Nicomorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",182,Noracymethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",183,Norlevorphanol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",184,Normethadone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",185,Normorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",186,Norpipanone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",187,OPIUM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",188,Oxymorphone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",189,OXYCODONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",190,Parafluorofentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",191,PAREGORIC,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",192,PAREPECTOLIN,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",193,PENTAZOCINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",195,Phenadoxone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",196,Phenampromide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",197,Phenanthrine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",198,Phenazocine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",199,Phenomorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",200,Phenoperidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",202,Pholcodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",203,Piminodine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",204,Piritramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",205,Proheptazine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",206,Properidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",207,Propiram,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",208,"Propoxyphene (Dextropropoxyphene, bulk (non-dosage forms))",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",209,Racemethorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",210,Racemoramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",211,Racemorphan,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",212,Sufentanil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",213,Thebacon,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",214,Thebaine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",215,Thiofentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",216,Tilidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",217,Trimeperidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",218,Butorphanol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",220,Alphacetylmethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",221,Beta-Hydroxy-3-methylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",222,Codeine & isoquinoline,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",223,Codeine-N-oxide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",224,Dextropropoxyphene (dosage forms),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",225,Difenenoxin,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",226,Dihydroetrophine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",227,Diprenorphine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",228,Levo-alphacetylmethadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",229,Levorphanol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",230,Methylthiofentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",231,Morphine-N-oxide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",232,Opium extract,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",233,Opium fluid extract,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",234,Opium Poppy,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",235,Opium Tincture,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",236,Phenylethyl-phenyl-acetoxypiperidine (PEPAP),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",237,Poppy Straw,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",238,Poppy Straw Concentrate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",239,Remifentanil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",240,Codeine combination product 90 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",241,Codeine preparations - 200 mg/100 ml or 100 gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",242,Difenoxin 1 mg/25ug AtSO4/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",243,Difenoxin preparations - 0.5 mg/25 ug AtSO4/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",244,Dihydrocodeine combination product 90 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",245,Dihydrocodeine preparations 10 mg/100 ml or 100 gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",246,Diphenoxylate preparations 2.5 mg/25 ug AtSO4,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",247,Ethylmorphine combination product 15 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",248,Ethylmorphine preparations 100 mg/100 ml or 100 gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",249,Hydrocodone & isoquinoline alkaloid<15 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",250,Hydrocodone combination product<15 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",251,Meperidine intermediate-A,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",252,Meperidine intermediate-B,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",253,Meperidine intermediate-C,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",254,Methadone intermediate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",255,Morphine combination product/50 mg/100 ml or gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",256,Opium combination product 25 mg/du,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",257,Opium preparations - 100 mg/100 ml or/100 gm,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",258,"Opium, granulated",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",259,"Opium, powdered",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",260,Oripavine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",295,"""Narcotics, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",300,ALPRAZOLAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",301,AMOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",302,Barbital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",303,BARBITURATES,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",304,BENZODIAZEPINES,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",305,Benzylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",306,Bromazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",307,BUTABARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",308,Butalbital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",309,Camazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",310,CARBAMATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",311,Chloral betaine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",312,Chloral Hydrate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",313,CHLORDIAZEPROXIDE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",314,Chlorhexadol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",315,Clobazam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",316,Clonazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",317,CLORAZEPATE DIPOTASSIUM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",318,Clotiazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",319,Cloxazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",320,Delorazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",321,DIAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",322,Estazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",323,ETHCHLORVYNOL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",324,Ethinamate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",325,Ethyl Ioflazepate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",326,Fiorinal,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",327,Fludiazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",328,Flunitrazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",330,GLUTETHIMIDE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",331,HALAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",332,Haloxazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",333,HEXOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",334,Hydroxyzine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",335,Ketazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",336,Loprazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",337,LORAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",338,Lormetazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",339,Mebutamate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",340,Mecloqualone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",341,Medazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",342,MEPHOBARBITAL (Methylphenobarbital),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",343,MEPROBAMATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",344,METHAQUALONE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",345,METHARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",346,Methohexital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",347,METHYPRYLON,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",348,Midazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",349,Nimetazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",350,Nitrazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",351,Nordiazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",352,OXAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",353,Oxazolam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",354,Paraldehyde,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",355,PENTOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",356,Petrichloral,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",357,Phencyclohexylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",358,PHENOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",359,Pinazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",360,PRAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",361,Quazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",362,SECOBARBITAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",363,Sulfondiethylmethane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",364,Sulfonethylmethane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",365,Sulfonmethane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",366,TALBUTAL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",367,TEMAZEPAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",368,Tetrazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",369,Thenylfentanyl,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",370,Thiamylal,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",371,Thiopental (Pentothal),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",372,Tiletamine/Zolazepam (Telazol),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",373,TRAIZOLAM,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",374,TYBAMATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",376,Carisoprodol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",377,Gamma Hydroxybutryate (GHB),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",378,Amobarbital & non-controlled active ingred.,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",379,Aprobarbital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",380,Barbituric Acid Derivative,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",383,Dexfenfluramine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",384,Flurazepam,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",385,Sibutramine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",386,Zaleplon,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",387,Zolpidem,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",388,Amobarbital suppository dosage form,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",389,Butobarbital (butethal),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",390,Embutramide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",391,Gamma Hydroxybutyric Acid preparations,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",393,Pentobarbital & noncontrolled active ingred.,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",394,Pentobarbital suppository dosage form,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",395,"""Depressants, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",396,Pregabalin,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",397,Secobarbital & noncontrolled active ingred.,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",398,Secobarbital suppository dosage form,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",399,Zopiclone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",400,AMPHETAMINE SULFATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",401,AMPHETAMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",402,BENZOYLECGONINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",403,BENZPHETAMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",404,Cathine (Norpseudoephedrine),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",405,Chlorphentermine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",406,Clortermine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",407,COCAINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",408,DEXTROAMPHETAMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",409,DIETHYLPROPION,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",410,Ecgonine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",411,Fencamfamin,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",412,FENETHYLLINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",413,Fenfluramine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",414,Fenproporex,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",415,MAZINDOL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",416,Menfenorex,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",417,METHAMPHETAMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",418,METHYLPHENIDATE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",419,N-Ethylamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",420,PEMOLINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",421,PHENDIMETRAZINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",422,PHENMETRAZINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",423,PHENTERMINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",424,Pipradrol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",425,Propylhexedrine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",426,Pyrovalerone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",427,SPA,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",428,Aminorex,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",429,Cathinone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",430,Coca Leaves,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",431,Dicholoralphenazone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",432,Methcathinone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",433,Modafinil,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",434,Vinbarbital,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",435,Methylone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",436,Lisdexamfetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",437,Methoxy-Methylenedioxyamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",438,"N, N-Dimethylamphetamine (Dimethylamphetamine)",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",439,N-Benzylpiperazine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",440,Stimulant compounds previously excepted,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",495,"""Stimulants, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",500,AMPHETAMINE VARIANTS,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",501,BUFOTENINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",503,Diethyltryptamine (DET),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",504,Dimethoxyamphetamine (DMA),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",505,Dimethyltryptamine(DMT),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",507,Dronabinol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",508,N-Ethyl-3-piperidyl benzilate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",509,IBOGAINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",511,LYSERGIC ACID,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",512,MESCALINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",513,Methylenedioxymethamphetamine (MDMA),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",514,Methoxyamphetamine (PMA),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",515,Methylenedioxyamphetamine (MDA),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",516,Nabilone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",517,PEYOTE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",518,Phenylacetone (P2P),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",519,PSILOCYBIN,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",520,PSILOCYN,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",521,Trimethoxy amphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",522,Ketamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",523,Alpha_Ethyltryptamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",524,Bromo-dimethoxyamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",525,Bromo-dimethoxyphenethylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",527,Lysergic Acid Amide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",528,Lysergic Acid Diethylamide (LSD),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",529,Methylaminorex,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",530,Methyl-dimethoxyamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",531,Methylenedioxy-N-ethylamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",532,Dimethylamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",533,N-Ethyl-1-phenylcyclohexylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",534,Alpha-methyltryptamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",535,Dimethoxyethylamphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",536,Dimethoxy-(n)-propylthiophenethylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",537,Methoxy-NN-diisopropyltryptamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",538,N-Hydroxymethylenedioxy-amphetamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",539,N-Methylpiperidyl benzilate,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",595,"""Hallucinogens, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",600,DELTA 9,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",601,HASHISH OIL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",602,HASHISH,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",603,MARIJUANA/Marihuana,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",604,MARINOL,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",605,Tetrahydrocannabinols (THC),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",695,"""Cannabinoid, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",700,Ethylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",701,Parahexyl (Synhexyl),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",702,PHENCYCLIDINE,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",703,PHENCYCLIDINE ANALOGS,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",704,phenylcyclohexylamine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",705,Piperidinocyclohexane-carbonitrile (PCC),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",706,"""Pyrrolidine (PCPy,PHP,TCPy)""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",707,Thiophend,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",708,Thienylcyclohexylpiperidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",709,Phenylcyclohexyl-Pyrrolidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",710,Thienyl Cyclohexyl Pyrrolidine,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",795,"""PCP, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",800,Boldenone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",801,Chlorotestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",803,Dehydrochlomethyltestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",804,Dihydrotesterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",805,Drostanolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",806,Ethylestrenol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",807,Fluoxymesterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",808,Formebulone (Formebolone),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",809,Mesterolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",810,Methandienone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",811,Methandranone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",812,Methandriol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",813,Methandrostenolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",814,Methenolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",815,Methyltestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",816,Mibolerone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",817,Nandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",818,Norethandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",819,Oxandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",820,Oxymesterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",821,Oxymetholone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",822,Stanolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",823,Stanozolol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",824,Testolactone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",825,Testosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",826,Trenbolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",827,Clostebol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",828,"Alpha, Beta-dihydroxy-alpha-androstane",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",829,Alpha-methyl-alpha-beta-dihydroxy-alpha-androstane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",830,Alpha-methyl-beta-beta-dihydroxy-alpha-androstane,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",831,Alpha-methyl-beta-beta-dihydroxy-androstene,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",832,Alpha-methyl-delta 1-dihydrotestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",833,Alpha-methyl-hydroxynandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",834,Androstanedione,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",835,Androstenediol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",836,Androstenedione,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",837,"Beta, beta-dihydroxy-alpha-androstane",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",838,Bolasterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",839,Calusterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",840,Delta 1-dihydrotestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",841,Furazabol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",842,Hydroxy-Nortestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",843,Hydroxytestosterone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",844,Mestanolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",845,Methyldienolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",846,Methyltrienolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",847,Norandrostenediol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",848,Norandrostenedione,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",849,Norbolethone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",850,Norclostebol,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",851,Normethandrolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",852,Stenbolone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",853,Tetrahydrogestrinone,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",895,"Anabolic Steroid, Type Unknown",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",900,Volatile Solvents (toluene),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",901,Plastic Cement (airplane glue),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",902,Paint and Paint Removers,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",903,"""Petroleum Products (gasoline, kerosene)""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",904,Lacquer Thinners,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",920,Anesthetic Gases,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",921,Amyl Nitrite,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",923,Butly Nitrite,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",924,Nitrous Oxide,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",925,Ether,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",926,Chloroform,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",940,Aerosols (hydrocarbon),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",941,Hair spray,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",942,Insecticides,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",943,Glass Chillers,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",944,Frying Pan Lubricants,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",995,"""Inhalants, Type Unknown""",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",996,Other Drug,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",997,"Test For Drug, Results Unknown",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",998,"Tested For Drugs, Drugs Found, Type unknown/Positive",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DRUGRES3,drugres3,Drug Test- Result (3),This data element identifies the drug test result for this person.,"The FARS analyst may have used any of the three data elements to code a result of a drug test. One must test all three data elements to ensure that the selected result is included. *See Specific Drug Listing in the FARS/NASS GES/CRSS Coding and Validation Manual. Starting in 2018 DRUGRES1, DRUGRES2, and DRUGRES3 were discontinued, and Drug Test Result (DRUGRES) is available in the Drugs data file.",999,Unknown if Tested,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,HOSPITAL,hospital,Transported to Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",0,Not Transported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,HOSPITAL,hospital,Transported to Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",1,EMS Air,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,HOSPITAL,hospital,Transported to Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",2,Law Enforcement,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,HOSPITAL,hospital,Transported to Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",3,EMS Unknown Mode,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,HOSPITAL,hospital,Transported to Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",4,Transported  Unknown Source,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,HOSPITAL,hospital,Transported to Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",5,EMS Ground,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,HOSPITAL,hospital,Transported to Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",6,Other,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,HOSPITAL,hospital,Transported to Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",8,Not Reported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,HOSPITAL,hospital,Transported to Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DOA,doa,Died at Scene/En Route,This data element identifies if this person died at the scene of the crash or en route to a hospital/medical facility.,Prior to 2019 the Data Element ID was P23/NM22. From 2019-2021 the Data Element ID was P23/NM23.,0,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,person,DOA,doa,Died at Scene/En Route,This data element identifies if this person died at the scene of the crash or en route to a hospital/medical facility.,Prior to 2019 the Data Element ID was P23/NM22. From 2019-2021 the Data Element ID was P23/NM23.,7,Died at Scene,1,1,1,1,1,1,1,1,1,1
FARS,person,DOA,doa,Died at Scene/En Route,This data element identifies if this person died at the scene of the crash or en route to a hospital/medical facility.,Prior to 2019 the Data Element ID was P23/NM22. From 2019-2021 the Data Element ID was P23/NM23.,8,Died En Route,1,1,1,1,1,1,1,1,1,1
FARS,person,DOA,doa,Died at Scene/En Route,This data element identifies if this person died at the scene of the crash or en route to a hospital/medical facility.,Prior to 2019 the Data Element ID was P23/NM22. From 2019-2021 the Data Element ID was P23/NM23.,9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",1,1,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",2,2,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",3,3,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",4,4,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",5,5,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",6,6,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",7,7,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",8,8,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",9,9,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",10,10,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",11,11,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",12,12,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",13,13,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",14,14,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",15,15,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",16,16,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",17,17,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",18,18,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",19,19,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",20,20,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",21,21,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",22,22,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",23,23,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",24,24,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",25,25,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",26,26,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",27,27,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",28,28,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",29,29,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",30,30,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",31,31,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",88,Not Applicable (Non-Fatal),1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",1,January,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",2,February,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",3,March,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",4,April,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",5,May,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",6,June,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",7,July,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",8,August,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",9,September,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",10,October,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",11,November,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",12,December,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",88,Not Applicable (Non-Fatal),1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2009,2009,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2010,2010,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2011,2011,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2012,2012,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2013,2013,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2014,2014,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2015,2015,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",8888,Not Applicable (Non-fatal),1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",9999,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",0,0:00-0:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",1,1:00-1:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",2,2:00-2:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",3,3:00-3:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",4,4:00-4:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",5,5:00-5:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",6,6:00-6:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",7,7:00-7:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",8,8:00-8:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",9,9:00-9:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",10,10:00-10:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",11,11:00-11:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",12,12:00-12:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",13,13:00-13:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",14,14:00-14:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",15,15:00-15:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",16,16:00-16:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",17,17:00-17:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",18,18:00-18:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",19,19:00-19:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",20,20:00-20:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",21,21:00-21:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",22,22:00-22:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",23,23:00-23:59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",88,Not Applicable (Non-fatal),1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",0,0,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",1,1,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",2,2,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",3,3,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",4,4,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",5,5,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",6,6,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",7,7,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",8,8,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",9,9,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",10,10,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",11,11,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",12,12,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",13,13,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",14,14,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",15,15,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",16,16,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",17,17,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",18,18,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",19,19,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",20,20,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",21,21,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",22,22,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",23,23,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",24,24,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",25,25,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",26,26,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",27,27,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",28,28,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",29,29,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",30,30,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",31,31,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",32,32,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",33,33,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",34,34,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",35,35,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",36,36,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",37,37,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",38,38,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",39,39,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",40,40,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",41,41,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",42,42,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",43,43,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",44,44,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",45,45,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",46,46,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",47,47,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",48,48,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",49,49,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",50,50,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",51,51,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",52,52,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",53,53,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",54,54,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",55,55,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",56,56,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",57,57,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",58,58,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",59,59,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",88,Not Applicable (Non-fatal),1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,person,DEATH_TM,death_tm,Death Time,This data element records the hour and minute of this person’s death utilizing the 24-hour clock format.,"Four digits; DEATH_HR followed by DEATH_MN, e.g., Valid Military Times 0643 for 6:43 a.m. Prior to 2019 the Data Element ID was P25/NM24. From 2019-2021 the Data Element ID was P25/NM25. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",NA,(Self-evident),1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,LAG_HRS,lag_hrs,Crash to Death Time (Hours),This data element records the hours between the time of the crash and this person’s time of death.,This is a computed data element.,NA,(Self-evident),1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,LAG_MINS,lag_mins,Crash to Death Minutes (Minutes),"This data element records the minutes, in addition to hours (“Lag Hours”), between the time of the crash and this person’s time of death.",This is a computed data element.,NA,(Self-evident),1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",5,Interfering With Driver,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",8,Mentally Challenged,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",9,Construction/Maintenance/Utility Worker,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",13,Motorized Wheelchair Rider,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",18,Mother of Dead Fetus/Infant Born Post Crash,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",21,Overloading or Improper Loading of Vehicle with Passengers or Cargo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",26,Following Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",28,Failure to Keep in Proper Lane,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",29,"Illegal Driving on Road Shoulder, in Ditch, on Sidewalk or on Median",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",32,Opening Vehicle Closure into Moving Traffic or While Vehicle is in Motion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",33,"Passing where Prohibited by Posted Signs, Pavement Markings, Hill or Curve, or School Bus Displaying Warning not to Pass Line",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",37,Traveling on Prohibited Trafficways,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",40,Passing Through or Around Barrier,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",41,Failure to Observe Warnings or Instructions on Vehicles Displaying Them,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",42,Failure to Signal Intentions,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",44,Driving too Fast for conditions or in Excess of Posted Maximum,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",45,Driving Less than Posted Minimum,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",47,Making Right Turn from Left Turn Lane or Making Left Turn from Right Turn Lane,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",51,Operator Inexperience,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",52,Unfamiliar with Roadway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",56,Non-Driver Flees Scene,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",57,Improper tire Pressure,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",58,Locked Wheel,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",59,Overcorrecting,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",60,"Rain, Snow, Fog, Smoke, Sand, Dust",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",61,"Reflected Glare, Bright Sunlight, Headlights",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",62,"Curve, Hill, or Other Design Features (including traffic signs, embankment)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",63,"Building, Billboard, Other Structures",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",64,"Trees, Crops, Vegetation",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",65,Motor Vehicle (including load),1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",66,Parked Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",67,Splash or Spray of Passing Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",68,Inadequate Lighting System,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",69,Obstructing Angles on Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",70,Mirrors,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",72,Other Visual Obstruction,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",73,Severe Crosswind,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",74,Wind From Passing Truck,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",75,Slippery or Loose Surface,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",76,Tire Blow-out or Flat,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",77,Debris or Objects in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",78,"Ruts, Holes, Bump in Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",80,Vehicle in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",81,Phantom Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",82,"Pedestrian, Pedal Cyclists or Persons on Personal Conveyances",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",83,"Ice, Snow, Slush, Water, Sand, Dirt, Oil, Wet Leaves on Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",86,Emergency Services Personnel,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",87,Police or Law Enforcement Officer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",88,"Seat Back Not in Normal Upright Position, Seat Back Reclined",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",89,Parked Motor Vehicle With Equipment Extending into the Travel Lane,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",90,Non-Motorist Pushing a Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",91,Portable Electronic Devices,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",92,Person in Ambulance Treatment Compartment,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",5,Interfering With Driver,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",8,Mentally Challenged,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",9,Construction/Maintenance/Utility Worker,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",13,Motorized Wheelchair Rider,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",18,Mother of Dead Fetus/Infant Born Post Crash,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",21,Overloading or Improper Loading of Vehicle with Passengers or Cargo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",26,Following Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",28,Failure to Keep in Proper Lane,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",29,"Illegal Driving on Road Shoulder, in Ditch, on Sidewalk or on Median",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",32,Opening Vehicle Closure into Moving Traffic or While Vehicle is in Motion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",33,"Passing where Prohibited by Posted Signs, Pavement Markings, Hill or Curve, or School Bus Displaying Warning not to Pass Line",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",37,Traveling on Prohibited Trafficways,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",40,Passing Through or Around Barrier,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",41,Failure to Observe Warnings or Instructions on Vehicles Displaying Them,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",42,Failure to Signal Intentions,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",44,Driving too Fast for conditions or in Excess of Posted Maximum,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",45,Driving Less than Posted Minimum,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",47,Making Right Turn from Left Turn Lane or Making Left Turn from Right Turn Lane,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",51,Operator Inexperience,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",52,Unfamiliar with Roadway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",56,Non-Driver Flees Scene,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",57,Improper tire Pressure,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",58,Locked Wheel,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",59,Overcorrecting,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",60,"Rain, Snow, Fog, Smoke, Sand, Dust",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",61,"Reflected Glare, Bright Sunlight, Headlights",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",62,"Curve, Hill, or Other Design Features (including traffic signs, embankment)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",63,"Building, Billboard, Other Structures",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",64,"Trees, Crops, Vegetation",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",65,Motor Vehicle (including load),1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",66,Parked Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",67,Splash or Spray of Passing Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",68,Inadequate Lighting System,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",69,Obstructing Angles on Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",70,Mirrors,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",72,Other Visual Obstruction,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",73,Severe Crosswind,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",74,Wind From Passing Truck,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",75,Slippery or Loose Surface,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",76,Tire Blow-out or Flat,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",77,Debris or Objects in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",78,"Ruts, Holes, Bump in Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",80,Vehicle in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",81,Phantom Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",82,"Pedestrian, Pedal Cyclists or Persons on Personal Conveyances",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",83,"Ice, Snow, Slush, Water, Sand, Dirt, Oil, Wet Leaves on Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",86,Emergency Services Personnel,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",87,Police or Law Enforcement Officer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",88,"Seat Back Not in Normal Upright Position, Seat Back Reclined",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",89,Parked Motor Vehicle With Equipment Extending into the Travel Lane,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",90,Non-Motorist Pushing a Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",91,Portable Electronic Devices,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",92,Person in Ambulance Treatment Compartment,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",5,Interfering With Driver,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",8,Mentally Challenged,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",9,Construction/Maintenance/Utility Worker,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",13,Motorized Wheelchair Rider,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",18,Mother of Dead Fetus/Infant Born Post Crash,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",21,Overloading or Improper Loading of Vehicle with Passengers or Cargo,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",26,Following Improperly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",28,Failure to Keep in Proper Lane,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",29,"Illegal Driving on Road Shoulder, in Ditch, on Sidewalk or on Median",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",32,Opening Vehicle Closure into Moving Traffic or While Vehicle is in Motion,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",33,"Passing where Prohibited by Posted Signs, Pavement Markings, Hill or Curve, or School Bus Displaying Warning not to Pass Line",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",37,Traveling on Prohibited Trafficways,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",40,Passing Through or Around Barrier,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",41,Failure to Observe Warnings or Instructions on Vehicles Displaying Them,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",42,Failure to Signal Intentions,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",44,Driving too Fast for conditions or in Excess of Posted Maximum,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",45,Driving Less than Posted Minimum,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",47,Making Right Turn from Left Turn Lane or Making Left Turn from Right Turn Lane,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",51,Operator Inexperience,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",52,Unfamiliar with Roadway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",56,Non-Driver Flees Scene,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",57,Improper tire Pressure,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",58,Locked Wheel,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",59,Overcorrecting,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",60,"Rain, Snow, Fog, Smoke, Sand, Dust",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",61,"Reflected Glare, Bright Sunlight, Headlights",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",62,"Curve, Hill, or Other Design Features (including traffic signs, embankment)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",63,"Building, Billboard, Other Structures",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",64,"Trees, Crops, Vegetation",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",65,Motor Vehicle (including load),1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",66,Parked Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",67,Splash or Spray of Passing Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",68,Inadequate Lighting System,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",69,Obstructing Angles on Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",70,Mirrors,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",72,Other Visual Obstruction,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",73,Severe Crosswind,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",74,Wind From Passing Truck,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",75,Slippery or Loose Surface,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",76,Tire Blow-out or Flat,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",77,Debris or Objects in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",78,"Ruts, Holes, Bump in Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",80,Vehicle in Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",81,Phantom Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",82,"Pedestrian, Pedal Cyclists or Persons on Personal Conveyances",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",83,"Ice, Snow, Slush, Water, Sand, Dirt, Oil, Wet Leaves on Road",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",86,Emergency Services Personnel,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",87,Police or Law Enforcement Officer,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",88,"Seat Back Not in Normal Upright Position, Seat Back Reclined",1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",89,Parked Motor Vehicle With Equipment Extending into the Travel Lane,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",90,Non-Motorist Pushing a Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",91,Portable Electronic Devices,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",92,Person in Ambulance Treatment Compartment,1,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,CERT_NO,cert_no,Death Certificate Number,NA,NA,NA,(Self-evident),1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,WORK_INJ,work_inj,Fatal Injury at Work,"This data element records whether the death certificate indicated this person was ""at work"" at the time of the crash.","In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",0,No,1,1,1,1,1,1,1,1,1,1
FARS,person,WORK_INJ,work_inj,Fatal Injury at Work,"This data element records whether the death certificate indicated this person was ""at work"" at the time of the crash.","In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",1,Yes,1,1,1,1,1,1,1,1,1,1
FARS,person,WORK_INJ,work_inj,Fatal Injury at Work,"This data element records whether the death certificate indicated this person was ""at work"" at the time of the crash.","In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",8,Not Applicable (not a fatality),1,1,1,1,1,1,1,1,1,1
FARS,person,WORK_INJ,work_inj,Fatal Injury at Work,"This data element records whether the death certificate indicated this person was ""at work"" at the time of the crash.","In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,person,HISPANIC,hispanic,Hispanic Origin,This data element records the Hispanic origin of this person from the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",0,Not A Fatality (not Applicable),1,1,1,1,1,1,1,1,1,1
FARS,person,HISPANIC,hispanic,Hispanic Origin,This data element records the Hispanic origin of this person from the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",1,Mexican,1,1,1,1,1,1,1,1,1,1
FARS,person,HISPANIC,hispanic,Hispanic Origin,This data element records the Hispanic origin of this person from the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",2,Puerto Rican,1,1,1,1,1,1,1,1,1,1
FARS,person,HISPANIC,hispanic,Hispanic Origin,This data element records the Hispanic origin of this person from the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",3,Cuban,1,1,1,1,1,1,1,1,1,1
FARS,person,HISPANIC,hispanic,Hispanic Origin,This data element records the Hispanic origin of this person from the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",4,Central or South American,1,1,1,1,1,1,1,1,1,1
FARS,person,HISPANIC,hispanic,Hispanic Origin,This data element records the Hispanic origin of this person from the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",5,European Spanish,1,1,1,1,1,1,1,1,1,1
FARS,person,HISPANIC,hispanic,Hispanic Origin,This data element records the Hispanic origin of this person from the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",6,"Hispanic, Origin Not Specified or Other Origin",1,1,1,1,1,1,1,1,1,1
FARS,person,HISPANIC,hispanic,Hispanic Origin,This data element records the Hispanic origin of this person from the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",7,Non-Hispanic,1,1,1,1,1,1,1,1,1,1
FARS,person,HISPANIC,hispanic,Hispanic Origin,This data element records the Hispanic origin of this person from the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",99,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",0,Not a Fatality (not Applicable),1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",1,White,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",2,Black,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",3,American Indian (includes Aleuts and Eskimos),1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",4,Chinese,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",5,Japanese,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",6,Hawaiian (includes Part-Hawaiian),1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",7,Filipino,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",18,Asian Indian,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",19,"Other Indian (includes South and Central America, any other, except American or Asian Indians)",1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",28,Korean,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",38,Samoan,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",48,Vietnamese,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",58,Guamanian,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",68,Other Asian or Pacific Islander,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",78,"Asian or Pacific Islander, no specific (individual) race",1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",97,"Multiple Races (individual races not specified; ex. ""mixed"")",1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",98,All other races,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",99,Unknown,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,0,Occupant of a Motor Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,1,At Intersection - In Marked Crosswalk,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,2,At Intersection-Unmarked / Unknown if Marked Crosswalk,1,1,1,1,1,1,1,NA,NA,NA
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,3,At Intersection - Not In Crosswalk,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,9,At Intersection - Unknown location,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,10,Not at Intersection - In  Marked Crosswalk,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,11,"Not at Intersection - On Roadway, Not in Marked Crosswalk",1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,13,"Not at Intersection - On Roadway, Crosswalk Availability Unknown",1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,14,Parking Lane/Zone,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,16,Bicycle Lane,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,20,Shoulder/Roadside,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,21,Sidewalk,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,22,Median/Crossing Island,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,23,Driveway Access,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,24,Shared-Use Path,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,25,Non- Trafficway Area,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,28,Other,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,99,Unknown Location,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,midrvacc,A1,a1,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,midrvacc,A2,a2,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,midrvacc,A3,a3,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,midrvacc,A4,a4,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,midrvacc,A5,a5,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,midrvacc,A6,a6,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,midrvacc,A7,a7,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,midrvacc,A8,a8,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,midrvacc,A9,a9,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,midrvacc,A10,a10,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,vsoe,VEVENTNUM,veventnum,Vehicle Event Number,This data element is the consecutive number assigned to each harmful and non-harmful event for this vehicle in chronological order.,The vehicle’s event number shows the chronological sequence of the qualifying harmful and non-harmful events involving a particular vehicle. Qualifying events are those that involve a motor vehicle in-transport or an object set in motion by a motor vehicle in-transport. Prior to 2015 the Data Element ID was C17.,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",1,Rollover/Overturn,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",2,Fire/Explosion,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",3,Immersion or Partial Immersion,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",4,Gas Inhalation,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",5,Fell/Jumped from Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",6,Injured In Vehicle (Non-Collision),1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",7,Other Non-Collision,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",8,Pedestrian,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",9,Pedalcyclist,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",10,Railway Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",11,Live Animal,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",12,Motor Vehicle In-Transport,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",14,Parked Motor Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",15,Non-Motorist on Personal Conveyance,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",16,Thrown or Falling Object,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",17,Boulder,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",18,Other Object (not fixed),1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",19,Building,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",20,Impact Attenuator/Crash Cushion,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",21,Bridge Pier or Support,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",23,Bridge Rail (Includes parapet),1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",24,Guardrail Face,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",25,Concrete Traffic Barrier,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",26,Other Traffic Barrier,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",30,Utility Pole/Light Support,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",31,"Other Post, Other Pole or Other Supports",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",32,Culvert,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",33,Curb,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",34,Ditch,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",35,Embankment,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",38,Fence,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",39,Wall,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",40,Fire Hydrant,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",41,Shrubbery,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",42,Tree (Standing Only),1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",43,Other Fixed Object,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",44,"Pavement Surface Irregularity (Ruts, Potholes, Grates, etc.)",1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",45,Working Motor Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",46,Traffic Signal Support,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",48,Snow Bank,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",49,Ridden Animal or Animal Drawn Conveyance,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",50,Bridge Overhead Structure,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",51,Jackknife (harmful to this vehicle),1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",52,Guardrail End,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",53,Mail Box,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",54,"Motor Vehicle In-Transport Strikes or is Struck by Cargo, Persons or Objects Set-in-Motion from/by Another Motor Vehicle In Transport",1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",55,Motor Vehicle in Motion Outside the Trafficway,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",57,Cable Barrier,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",58,Ground,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",59,Traffic Sign Support,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",60,Cargo/Equipment Loss or Shift (non-harmful),1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",61,"Equipment Failure (blown tire, brake failure, etc)",1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",62,Separation of Units,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",63,Ran Off Roadway - Right,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",64,Ran Off Roadway - Left,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",65,Cross Median,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",66,Downhill Runaway,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",67,Vehicle Went Airborne,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",68,Cross Centerline,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",69,Re-entering Roadway,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",70,"Non-harmful, Swaying Trailer/Jackknife",1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",71,End Departure,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",72,Cargo/Equipment Loss or Shift (harmful to this vehicle),1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",73,Object Fell From Motor Vehicle In-Transport,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",79,Ran off Roadway - Direction Unknown,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,0,Non-Collision,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,1,1 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,2,2 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,3,3 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,4,4 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,5,5 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,6,6 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,7,7 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,8,8 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,9,9 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,10,10 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,11,11 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,12,12 Clock Point,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,13,Top,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,14,Undercarriage,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,18,Cargo/Vehicle Parts Set-In-Motion,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,19,Other Objects Set-In-Motion,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,55,Non-Harmful Event,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,61,Left,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,62,Left-Front Side,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,63,Left-Back Side,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,77,Not a Motor Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,81,Right,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,82,Right-Front Side,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,83,Right-Back Side,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,distract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,distract,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",0,Not Distracted,1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",1,Looked But Did Not See,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",3,By Other Occupant(s),1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",4,By a Moving Object in Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",5,While Talking or Listening to Cellular Phone,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",6,While Manipulating Cellular Phone,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",7,Adjusting Audio Or Climate Controls,1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",9,While Using Other Component/Controls Integral to Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",10,While Using or Reaching for Device/Object Brought into Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",12,"Distracted by Outside Person, Object or Event",1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",13,Eating or Drinking,1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",14,Smoking Related,1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",15,Other Cellular Phone Related,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",16,No Driver Present/Unknown if Driver present,1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",17,Distraction/Inattention,1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",18,Distraction/Careless,1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",19,Careless/Inattentive,1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",92,"Distraction (Distracted), Details Unknown",1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",93,"Inattention (Inattentive), Details Unknown",1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",96,Not Reported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",97,Lost in Thought / Day dreaming,1,1,1,1,1,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",98,Other Distraction,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",99,Unknown if Distracted,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",0,None/Apparently Normal,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",1,"Ill, Blackout",1,1,1,1,1,1,1,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",2,Asleep or Fatigued,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",3,"Walking with a Cane or Crutches, etc.",1,1,1,1,1,1,1,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",4,Paraplegic Or Restricted To A Wheelchair,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",5,Impaired Due to Previous Injury,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",6,Deaf,1,1,1,1,1,1,1,NA,NA,NA
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",7,Blind,1,1,1,1,1,1,1,NA,NA,NA
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",8,"Emotional (depressed, angry, disturbed, etc)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",9,"Under the Influence of Alcohol, Drugs or Medication",1,1,1,1,1,1,1,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",10,Physical Impairment - No Details,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",95,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",96,Other Physical Impairment,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",99,Unknown if Impaired,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,factor,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,factor,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",1,Tires,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",2,Brake System,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",3,Steering,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",4,Suspension,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",5,Power Train,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",6,Exhaust System,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",7,Head Lights,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",8,Signal Lights,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",9,Other Lights,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",10,Wipers,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",11,Wheels,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",12,Mirrors,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",13,Windows/Windshield,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",14,"Body, Doors",1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",15,Truck Coupling/Trailer Hitch/Safety Chains,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",16,Safety Systems,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",17,Vehicle Contributing Factors - No Details,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",97,Other,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",98,Not Reported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,maneuver,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,maneuver,MDRMANAV,mdrmanav,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,0,Driver Did Not Maneuver to Avoid,1,1,1,1,1,1,NA,NA,NA,NA
FARS,maneuver,MDRMANAV,mdrmanav,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,1,Object,1,1,1,1,1,1,NA,NA,NA,NA
FARS,maneuver,MDRMANAV,mdrmanav,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,2,"Poor Road Conditions (Puddle, Ice, Pothole, etc.)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,maneuver,MDRMANAV,mdrmanav,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,3,Live Animal,1,1,1,1,1,1,NA,NA,NA,NA
FARS,maneuver,MDRMANAV,mdrmanav,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,4,Motor Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,maneuver,MDRMANAV,mdrmanav,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,5,"Pedestrian, Pedalcyclist or Other Non-Motorist",1,1,1,1,1,1,NA,NA,NA,NA
FARS,maneuver,MDRMANAV,mdrmanav,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,92,Phantom/Non-Contact Motor Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,maneuver,MDRMANAV,mdrmanav,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,95,No Driver Present/Unknown if Driver present,1,1,1,1,1,1,NA,NA,NA,NA
FARS,maneuver,MDRMANAV,mdrmanav,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,98,Not Reported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,maneuver,MDRMANAV,mdrmanav,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,violatn,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,violatn,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,0,None,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,1,Manslaughter or homicide,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,2,Willful reckless driving; driving to endanger; negligent driving,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,3,"Unsafe reckless (not willful, wanton reckless) driving",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,4,"Inattentive, careless, improper driving",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,5,Fleeing or eluding police,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,6,"Fail to obey police, fireman, authorized person directing traffic",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,7,"Hit-and-run, fail to stop after crash",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,8,"Fail to give aid, info., wait for police after crash",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,9,Serious violation resulting in death,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,11,Driving while intoxicated (alcohol or drugs) or BAC above limit (any detectable BAC for CDLs),1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,12,Driving while impaired,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,13,Driving under influence of substance not intended to intoxicate,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,14,Drinking while operating,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,15,Illegal possession of alcohol or drugs,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,16,Driving with detectable alcohol,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,18,Refusal to submit to chemical test,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,19,"Alcohol, drug, or impairment violations generally",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,21,Racing,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,22,Speeding (above the speed limit),1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,23,Speed greater than reasonable & prudent (not necessarily over the limit),1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,24,"Exceeding special speed limit (e.g. for trucks, buses, cycles, or on bridge, in school zone, etc.)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,25,"Energy speed (exceeding 55 mph, non-pointable)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,26,Driving too slowly,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,29,"Speed related violations, generally",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,31,Fail to stop for red signal,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,32,Fail to stop for flashing red,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,33,"Violation of turn on red (fail to stop & yield, yield to pedestrians before turning)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,34,Fail to obey flashing signal (yellow or red),1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,35,Fail to obey signal generally,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,36,Violate RR grade crossing device/regulations,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,37,Fail to obey stop sign,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,38,Fail to obey yield sign,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,39,Fail to obey traffic control device,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,41,"Turn in violation of traffic control (disobey signs, turn arrow or pavement markings; not a right on red violation)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,42,"Improper method & position of turn (too wide, wrong lane)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,43,Fail to signal for turn or stop,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,45,Fail to yield to emergency vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,46,Fail to yield generally,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,48,Enter intersection when space insufficient,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,49,"Turn, yield, signaling violations generally",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,51,Driving wrong way on one-way road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,52,"Driving on left, wrong side of road, generally",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,53,"Improper, unsafe passing",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,54,Pass on right (drive off pavement to pass),1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,55,Pass stopped school bus,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,56,Fail to give way when overtaken,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,58,Following too closely,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,59,"Wrong side, passing, following violations, generally",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,61,Unsafe or prohibited lane change,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,62,"Improper use of lane (enter of 3-lane road, HOV designated lane)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,63,"Certain traffic to use right lane (trucks, slow moving, etc.)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,66,"Motorcycle lane violations (more than two per lane, riding between lanes, etc.)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,67,Motorcyclist attached to another vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,69,"Lane violations, generally",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,71,Driving while license withdrawn,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,72,Other driver license violations,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,73,"Commercial driver violations (log book, hours, permits carried)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,74,Vehicle registration violations,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,75,Fail to carry insurance card,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,76,Driving uninsured vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,79,Non-moving violations generally,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,81,Lamp violations,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,82,Brake violations,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,83,Failure to require restraint use (by self or passengers),1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,84,"Motorcycle equipment violations (helmet, special equipment)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,85,Violation of hazardous cargo regulations,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,86,"Size, weight, load violations",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,89,Equipment violations generally,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,91,Parking,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,92,"Theft, unauthorized use of motor vehicle",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,93,"Driving where prohibited (sidewalk, limited access, off truck route)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,95,No Driver Present/Unknown if Driver Present,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,97,Not Reported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,98,"Other moving violation (coasting, backing, opening door)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,99,Unknown Violation(s),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,vision,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,vision,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,0,No Obstruction Noted,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,1,"Rain, Snow, Fog, Smoke, Sand, Dust",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,2,"Reflected Glare, Bright Sunlight, Headlights",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,3,"Curve, Hill or Other Roadway Design Feature",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,4,"Building, Billboard, Other Structure",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,5,"Trees, Crops, Vegetation",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,6,In-Transport Motor Vehicle (including load),1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,7,"Not In-Transport Motor Vehicle (parked, working)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,8,Splash or Spray of Passing Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,9,Inadequate Defrost or Defog System,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,10,Inadequate Vehicle Lighting System,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,11,Obstruction Interior to the Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,12,External Mirrors,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,13,Broken or Improperly Cleaned Windshield,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,14,Obstructing Angles on Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,95,No Driver Present/Unknown if Driver present,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,97,Vision Obscured - No Details,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,98,Other Visual Obstruction,1,1,1,1,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,damage,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,damage,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,1,1 Clock Value,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,2,2 Clock Value,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,3,3 Clock Value,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,4,4 Clock Value,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,5,5 Clock Value,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,6,6 Clock Value,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,7,7 Clock Value,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,8,8 Clock Value,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,9,9 Clock Value,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,10,10 Clock Value,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,11,11 Clock Value,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,12,12 Clock Value,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,13,Top,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,14,Undercarriage,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,15,No Damage,1,1,1,1,1,1,NA,NA,NA,NA
FARS,damage,MDAREAS,mdareas,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,99,Damage Areas Unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PER_NO,per_no,Person Number,"This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files.","Each occupant of the vehicle is numbered, and each non-occupant is numbered; in the case of a non-occupant the vehicle number is zero. The numbers for occupants are consecutive for each vehicle beginning with 1. Numbers are never skipped. Drivers do not have to be coded 1. Non- Occupants are identified by vehicle number 0 and are numbered consecutively starting with 1 for each non-motorist. To get drivers see data element PER_TYP under Person Type. PER_NO can be used in merges, e.g., when merging the FARS person data file with the multiple cause of death file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,1,Driver of a Motor Vehicle In-Transport,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,2,Passenger of a Motor Vehicle In-Transport,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,3,Occupant of a Motor Vehicle Not In- Transport,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,4,Occupant of a Non-Motor Vehicle Transport Device,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,5,Pedestrian,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,6,Bicyclist,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,7,Other Cyclist,1,1,1,1,1,1,1,1,NA,NA
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,8,Persons on Personal Conveyances,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,9,Unknown Occupant Type in a Motor Vehicle In- Transport,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,10,Persons In/On Buildings,1,1,1,1,1,1,1,1,NA,NA
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,19,Unknown Type of Non-Motorist,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,0,Less than One Year,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,1,1 Year,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,2,2 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,3,3 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,4,4 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,5,5 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,6,6 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,7,7 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,8,8 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,9,9 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,10,10 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,11,11 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,12,12 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,13,13 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,14,14 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,15,15 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,16,16 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,17,17 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,18,18 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,19,19 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,20,20 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,21,21 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,22,22 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,23,23 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,24,24 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,25,25 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,26,26 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,27,27 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,28,28 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,29,29 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,30,30 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,31,31 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,32,32 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,33,33 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,34,34 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,35,35 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,36,36 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,37,37 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,38,38 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,39,39 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,40,40 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,41,41 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,42,42 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,43,43 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,44,44 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,45,45 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,46,46 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,47,47 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,48,48 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,49,49 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,50,50 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,51,51 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,52,52 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,53,53 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,54,54 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,55,55 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,56,56 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,57,57 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,58,58 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,59,59 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,60,60 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,61,61 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,62,62 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,63,63 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,64,64 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,65,65 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,66,66 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,67,67 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,68,68 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,69,69 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,70,70 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,71,71 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,72,72 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,73,73 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,74,74 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,75,75 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,76,76 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,77,77 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,78,78 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,79,79 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,80,80 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,81,81 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,82,82 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,83,83 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,84,84 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,85,85 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,86,86 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,87,87 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,88,88 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,89,89 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,90,90 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,91,91 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,92,92 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,93,93 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,94,94 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,95,95 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,96,96 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,97,97 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,98,98 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,99,99 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,100,100 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,101,101 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,102,102 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,103,103 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,104,104 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,105,105 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,106,106 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,107,107 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,108,108 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,109,109 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,110,110 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,111,111 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,112,112 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,113,113 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,114,114 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,115,115 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,116,116 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,117,117 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,118,118 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,119,119 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,120,120 Years,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,998,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,999,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,pbtype,PBSEX,pbsex,Sex,This data element identifies the sex of the person involved in the crash.,NA,1,Male,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBSEX,pbsex,Sex,This data element identifies the sex of the person involved in the crash.,NA,2,Female,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBSEX,pbsex,Sex,This data element identifies the sex of the person involved in the crash.,NA,8,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBSEX,pbsex,Sex,This data element identifies the sex of the person involved in the crash.,NA,9,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,pbtype,PBCWALK,pbcwalk,Marked Crosswalk,This data element indicates if a marked crosswalk was present at the crash site.,This data element is applicable to both pedestrians and bicyclists. Prior to 2022 the Element Data ID was NM9-PB27.,0,None Noted,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBCWALK,pbcwalk,Marked Crosswalk,This data element indicates if a marked crosswalk was present at the crash site.,This data element is applicable to both pedestrians and bicyclists. Prior to 2022 the Element Data ID was NM9-PB27.,1,Yes,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBCWALK,pbcwalk,Marked Crosswalk,This data element indicates if a marked crosswalk was present at the crash site.,This data element is applicable to both pedestrians and bicyclists. Prior to 2022 the Element Data ID was NM9-PB27.,9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBSWALK,pbswalk,Sidewalk Presence,This data element indicates if a sidewalk was present at the crash site.,This data element is applicable to both pedestrians and bicyclists. Prior to 2022 the Element Data ID was NM9-PB28.,0,None Noted,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBSWALK,pbswalk,Sidewalk Presence,This data element indicates if a sidewalk was present at the crash site.,This data element is applicable to both pedestrians and bicyclists. Prior to 2022 the Element Data ID was NM9-PB28.,1,Yes,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBSWALK,pbswalk,Sidewalk Presence,This data element indicates if a sidewalk was present at the crash site.,This data element is applicable to both pedestrians and bicyclists. Prior to 2022 the Element Data ID was NM9-PB28.,9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBSZONE,pbszone,School Zone,This data element indicates if the crash occurred in a school zone.,This data element is applicable to both pedestrians and bicyclists. Prior to 2022 the Element Data ID was NM9-PB29.,0,None Noted,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBSZONE,pbszone,School Zone,This data element indicates if the crash occurred in a school zone.,This data element is applicable to both pedestrians and bicyclists. Prior to 2022 the Element Data ID was NM9-PB29.,1,Yes,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PBSZONE,pbszone,School Zone,This data element indicates if the crash occurred in a school zone.,This data element is applicable to both pedestrians and bicyclists. Prior to 2022 the Element Data ID was NM9-PB29.,9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,0,Not a Pedestrian,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,120,Dispute-Related,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,130,Pedestrian on Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,140,Vehicle-Vehicle / Object,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,150,Motor Vehicle Loss of Control,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,160,Pedestrian Loss of Control,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,190,Other Unusual Circumstances,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,211,Backing Vehicle - Non-Trafficway - Driveway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,212,Backing Vehicle - Driveway Access,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,213,Backing Vehicle - Trafficway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,214,Backing Vehicle - Non-Trafficway - Parking Lot,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,219,Backing Vehicle - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,220,Driverless Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,230,Disabled Vehicle-Related,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,240,Emergency Vehicle-Related,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,250,Play Vehicle-Related,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,311,Working in Roadway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,312,Playing in Roadway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,313,Lying in Roadway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,320,Entering / Exiting Parked or Stopped Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,330,Mailbox-Related,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,341,Transit Bus Related,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,342,School Bus Stop-Related,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,360,Ice Cream / Vendor Truck-Related,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,410,Walking/Running Along Roadway With Traffic - From Behind,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,420,Walking/Running Along Roadway With Traffic - From Front,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,430,Walking/Running Along Roadway Against Traffic - From Behind,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,440,Walking/Running Along Roadway Against Traffic - From Front,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,459,Walking/Running Along Roadway - Direction / Position Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,461,Motorist Entering Driveway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,465,Motorist Exiting Driveway or Alley,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,469,Driveway Crossing - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,510,Waiting to Cross - Vehicle Turning,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,520,Waiting to Cross - Vehicle Not Turning,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,590,Waiting to Cross - Vehicle Action Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,610,Standing in Roadway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,620,Walking in Roadway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,680,Not At Intersection - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,690,At Intersection - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,710,Multiple Threat,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,730,Trapped,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,741,Dash,1,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,742,Dart-Out,1,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,760,Pedestrian Failed to Yield,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,770,Motorist Failed to Yield,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,781,Motorist Left Turn - Parallel Paths,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,782,Motorist Left Turn - Perpendicular Paths,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,791,Motorist Right Turn - Parallel Paths,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,792,Motorist Right Turn on Red - Parallel Paths,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,794,Motorist Right Turn on Red - Perpendicular Paths,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,795,Motorist Right Turn - Perpendicular Paths,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,799,Motorist Turn / Merge - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,830,Non-Trafficway - Parking Lot,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,890,Non-Trafficway - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,900,Other - Unknown Location,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,910,Crossing an Expressway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,0,Not a Cyclist,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,111,Motorist Turning Error - Left turn,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,112,Motorist Turning Error - Right turn,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,113,Motorist Turning Error - Other,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,114,Bicyclist Turning Error - Left turn,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,115,Bicyclist Turning Error - Right turn,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,116,Bicyclist Turning Error - Other,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,121,Bicyclist Lost Control - Mechanical problems,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,122,"Bicyclist Lost Control - Oversteering, Improper Braking, Speed",1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,123,Bicyclist Lost Control - Alcohol / Drug Impairment,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,124,Bicyclist Lost Control - Surface Conditions,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,129,Bicyclist Lost Control - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,131,Motorist Lost Control - Mechanical problems,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,132,"Motorist Lost Control - Oversteering, Improper Braking, Speed",1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,133,Motorist Lost Control - Alcohol / Drug Impairment,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,134,Motorist Lost Control - Surface Conditions,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,139,Motorist Lost Control - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,141,Motorist Drive Out - Sign-Controlled Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,142,Bicyclist Ride Out - Sign-Controlled Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,143,Motorist Drive Through - Sign-Controlled Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,144,Bicyclist Ride Through - Sign-Controlled Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,147,Multiple Threat - Sign-Controlled Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,148,Sign-Controlled Intersection - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,151,Motorist Drive Out - Right-Turn-on-Red,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,152,Motorist Drive Out - Signalized Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,153,Bicyclist Ride Out - Signalized Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,154,Motorist Drive Through - Signalized Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,155,Bicyclist Ride Through - Signalized Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,156,Bicyclist Failed to Clear - Trapped,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,157,Bicyclist Failed to Clear - Multiple Threat,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,158,Signalized Intersection - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,159,Bicyclist Failed to Clear - Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,160,Crossing Paths - Uncontrolled Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,180,Crossing Paths - Intersection - Other / Unknown Control,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,211,Motorist Left Turn- Same Direction,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,212,Motorist Left Turn- Opposite Direction,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,213,Motorist Right Turn - Same Direction,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,214,Motorist right Turn - Opposite Direction,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,215,Motorist Drive-In/Out Parking,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,216,Bus / Delivery Vehicle Pullover,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,217,Motorist Right Turn on Red - Same Direction,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,218,Motorist Right Turn on Red - Opposite Direction,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,219,Motorist Turn / Merge - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,221,Bicyclist Left Turn - Same Direction,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,222,Bicyclist Left Turn - Opposite Direction,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,223,Bicyclist Right Turn - Same Direction,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,224,Bicyclist Right Turn - Opposite Direction,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,225,Bicyclist Ride Out - Parallel Path,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,231,Motorist Overtaking - Undetected Bicyclist,1,1,1,1,1,1,1,NA,NA,NA
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,232,Motorist Overtaking - Misjudged Space,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,235,Motorist Overtaking - Bicyclist Swerved,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,239,Motorist Overtaking - Other/ Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,241,Bicyclist Overtaking - Passing on Right,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,242,Bicyclist Overtaking - Passing on Left,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,243,Bicyclist Overtaking - Parked Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,244,Bicyclist Overtaking - Extended Door,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,249,Bicyclist Overtaking - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,250,Wrong-Way / Wrong-Side - Bicyclist,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,255,Wrong-Way / Wrong-Side - Motorist,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,259,Wrong-Way / Wrong-Side - Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,280,Parallel Paths - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,311,Bicyclist Ride Out - Residential Driveway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,312,Bicyclist Ride-Out - Commercial Driveway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,313,"Bicyclist Ride-Out - Driveway, Unknown Type",1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,318,Bicyclist Ride Out - Other Midblock,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,319,Bicyclist Ride Out - Midblock - Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,321,Motorist Drive Out - Residential Driveway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,322,Motorist Drive-Out - Commercial Driveway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,323,"Motorist Drive-Out - Driveway, Unknown Type",1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,328,Motorist Drive Out - Other Midblock,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,329,Motorist Drive Out - Midblock - Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,357,Multiple Threat -  Midblock,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,380,Crossing Paths - Midblock - Other / Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,610,Backing Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,700,Play Vehicle-Related,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,800,Unusual Circumstances,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,910,Non-Roadway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,970,Unknown Approach Paths,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,980,Unknown Location,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDLOC,pedloc,Pedestrian Crash Location,This data element identifies where the pedestrian crash occurred with respect to an intersection.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB31.,1,At Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDLOC,pedloc,Pedestrian Crash Location,This data element identifies where the pedestrian crash occurred with respect to an intersection.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB31.,2,Intersection-Related,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDLOC,pedloc,Pedestrian Crash Location,This data element identifies where the pedestrian crash occurred with respect to an intersection.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB31.,3,Not At Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDLOC,pedloc,Pedestrian Crash Location,This data element identifies where the pedestrian crash occurred with respect to an intersection.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB31.,4,Non-Trafficway Location,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDLOC,pedloc,Pedestrian Crash Location,This data element identifies where the pedestrian crash occurred with respect to an intersection.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB31.,7,Not a Pedestrian,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDLOC,pedloc,Pedestrian Crash Location,This data element identifies where the pedestrian crash occurred with respect to an intersection.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB31.,9,Unknown,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,BIKELOC,bikeloc,Bicyclist Crash Location,This data element identifies where the bicyclist crash occurred with respect to an intersection.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB31B.,1,At Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKELOC,bikeloc,Bicyclist Crash Location,This data element identifies where the bicyclist crash occurred with respect to an intersection.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB31B.,2,Intersection-Related,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKELOC,bikeloc,Bicyclist Crash Location,This data element identifies where the bicyclist crash occurred with respect to an intersection.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB31B.,3,Not At Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKELOC,bikeloc,Bicyclist Crash Location,This data element identifies where the bicyclist crash occurred with respect to an intersection.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB31B.,4,Non-Trafficway Location,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKELOC,bikeloc,Bicyclist Crash Location,This data element identifies where the bicyclist crash occurred with respect to an intersection.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB31B.,7,Not a Cyclist,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKELOC,bikeloc,Bicyclist Crash Location,This data element identifies where the bicyclist crash occurred with respect to an intersection.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB31B.,9,Unknown,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,PEDPOS,pedpos,Pedestrian Position,This data element identifies the position/location of the pedestrian with respect to the trafficway when contacted.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB32.,1,Intersection Area,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDPOS,pedpos,Pedestrian Position,This data element identifies the position/location of the pedestrian with respect to the trafficway when contacted.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB32.,2,"Within a crosswalk, marked or unmarked",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,PEDPOS,pedpos,Pedestrian Position,This data element identifies the position/location of the pedestrian with respect to the trafficway when contacted.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB32.,3,"On a roadway, in a travel lane",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,PEDPOS,pedpos,Pedestrian Position,This data element identifies the position/location of the pedestrian with respect to the trafficway when contacted.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB32.,4,Paved Shoulder / Bicycle Lane / Parking Lane,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDPOS,pedpos,Pedestrian Position,This data element identifies the position/location of the pedestrian with respect to the trafficway when contacted.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB32.,5,Sidewalk / Shared-Use Path / Driveway Access,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDPOS,pedpos,Pedestrian Position,This data element identifies the position/location of the pedestrian with respect to the trafficway when contacted.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB32.,6,"Other road right-of-way (unpaved shoulder, etc.)",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,PEDPOS,pedpos,Pedestrian Position,This data element identifies the position/location of the pedestrian with respect to the trafficway when contacted.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB32.,7,Non-Trafficway - Driveway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDPOS,pedpos,Pedestrian Position,This data element identifies the position/location of the pedestrian with respect to the trafficway when contacted.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB32.,8,Non-Trafficway - Parking Lot/Other,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDPOS,pedpos,Pedestrian Position,This data element identifies the position/location of the pedestrian with respect to the trafficway when contacted.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB32.,9,Other/Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDPOS,pedpos,Pedestrian Position,This data element identifies the position/location of the pedestrian with respect to the trafficway when contacted.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB32.,77,Not a Pedestrian,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKEPOS,bikepos,Bicyclist Position,This data element identifies the position/location of the bicyclist with respect to the trafficway when contacted.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB32B.,1,"On a roadway, in a shared travel lane",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,BIKEPOS,bikepos,Bicyclist Position,This data element identifies the position/location of the bicyclist with respect to the trafficway when contacted.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB32B.,2,Bicycle Lane / Paved Shoulder / Parking Lane,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKEPOS,bikepos,Bicyclist Position,This data element identifies the position/location of the bicyclist with respect to the trafficway when contacted.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB32B.,3,Sidewalk  / Crosswalk / Driveway Access,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKEPOS,bikepos,Bicyclist Position,This data element identifies the position/location of the bicyclist with respect to the trafficway when contacted.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB32B.,4,Shared-Use Path,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKEPOS,bikepos,Bicyclist Position,This data element identifies the position/location of the bicyclist with respect to the trafficway when contacted.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB32B.,5,Non-Trafficway - Driveway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKEPOS,bikepos,Bicyclist Position,This data element identifies the position/location of the bicyclist with respect to the trafficway when contacted.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB32B.,6,Non-Trafficway - Parking Lot/Other,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKEPOS,bikepos,Bicyclist Position,This data element identifies the position/location of the bicyclist with respect to the trafficway when contacted.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB32B.,7,Not a Cyclist,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKEPOS,bikepos,Bicyclist Position,This data element identifies the position/location of the bicyclist with respect to the trafficway when contacted.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB32B.,8,"Other (e.g., unpaved shoulder, worn path, etc.)",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,BIKEPOS,bikepos,Bicyclist Position,This data element identifies the position/location of the bicyclist with respect to the trafficway when contacted.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB32B.,9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDDIR,peddir,Pedestrian Direction,This data element identifies the initial direction of travel of the pedestrian prior to being contacted in the crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB33.,1,Northbound,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDDIR,peddir,Pedestrian Direction,This data element identifies the initial direction of travel of the pedestrian prior to being contacted in the crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB33.,2,Eastbound,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDDIR,peddir,Pedestrian Direction,This data element identifies the initial direction of travel of the pedestrian prior to being contacted in the crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB33.,3,Southbound,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDDIR,peddir,Pedestrian Direction,This data element identifies the initial direction of travel of the pedestrian prior to being contacted in the crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB33.,4,Westbound,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDDIR,peddir,Pedestrian Direction,This data element identifies the initial direction of travel of the pedestrian prior to being contacted in the crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB33.,7,Not a Pedestrian,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDDIR,peddir,Pedestrian Direction,This data element identifies the initial direction of travel of the pedestrian prior to being contacted in the crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB33.,8,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDDIR,peddir,Pedestrian Direction,This data element identifies the initial direction of travel of the pedestrian prior to being contacted in the crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB33.,9,Unknown Initial Direction of Travel,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,BIKEDIR,bikedir,Bicyclist Direction,This data element identifies the initial travel direction of the bicyclist with respect to the flow of traffic prior to being contacted in the crash.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB33B.,1,With Traffic,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKEDIR,bikedir,Bicyclist Direction,This data element identifies the initial travel direction of the bicyclist with respect to the flow of traffic prior to being contacted in the crash.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB33B.,2,Facing Traffic,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKEDIR,bikedir,Bicyclist Direction,This data element identifies the initial travel direction of the bicyclist with respect to the flow of traffic prior to being contacted in the crash.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB33B.,3,Not applicable,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKEDIR,bikedir,Bicyclist Direction,This data element identifies the initial travel direction of the bicyclist with respect to the flow of traffic prior to being contacted in the crash.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB33B.,7,Not a Cyclist,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKEDIR,bikedir,Bicyclist Direction,This data element identifies the initial travel direction of the bicyclist with respect to the flow of traffic prior to being contacted in the crash.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB33B.,9,Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTDIR,motdir,Motorist Direction,This data element identifies the initial direction of travel of the motorist prior to being involved in a pedestrian crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB34.,1,Northbound,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTDIR,motdir,Motorist Direction,This data element identifies the initial direction of travel of the motorist prior to being involved in a pedestrian crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB34.,2,Eastbound,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTDIR,motdir,Motorist Direction,This data element identifies the initial direction of travel of the motorist prior to being involved in a pedestrian crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB34.,3,Southbound,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTDIR,motdir,Motorist Direction,This data element identifies the initial direction of travel of the motorist prior to being involved in a pedestrian crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB34.,4,Westbound,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTDIR,motdir,Motorist Direction,This data element identifies the initial direction of travel of the motorist prior to being involved in a pedestrian crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB34.,7,Not a Pedestrian,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTDIR,motdir,Motorist Direction,This data element identifies the initial direction of travel of the motorist prior to being involved in a pedestrian crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB34.,8,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTDIR,motdir,Motorist Direction,This data element identifies the initial direction of travel of the motorist prior to being involved in a pedestrian crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB34.,9,Unknown Initial Direction of Travel,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTMAN,motman,Motorist Maneuver,This data element identifies if the motorist was engaged in a turning maneuver at an intersection prior to being involved in a pedestrian crash. The data element indicates the maneuver being made by the motorist at the time of a pedestrian collision.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB35.,1,Left Turn,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTMAN,motman,Motorist Maneuver,This data element identifies if the motorist was engaged in a turning maneuver at an intersection prior to being involved in a pedestrian crash. The data element indicates the maneuver being made by the motorist at the time of a pedestrian collision.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB35.,2,Right Turn,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTMAN,motman,Motorist Maneuver,This data element identifies if the motorist was engaged in a turning maneuver at an intersection prior to being involved in a pedestrian crash. The data element indicates the maneuver being made by the motorist at the time of a pedestrian collision.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB35.,3,Straight through,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTMAN,motman,Motorist Maneuver,This data element identifies if the motorist was engaged in a turning maneuver at an intersection prior to being involved in a pedestrian crash. The data element indicates the maneuver being made by the motorist at the time of a pedestrian collision.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB35.,7,Not a Pedestrian,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTMAN,motman,Motorist Maneuver,This data element identifies if the motorist was engaged in a turning maneuver at an intersection prior to being involved in a pedestrian crash. The data element indicates the maneuver being made by the motorist at the time of a pedestrian collision.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB35.,8,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTMAN,motman,Motorist Maneuver,This data element identifies if the motorist was engaged in a turning maneuver at an intersection prior to being involved in a pedestrian crash. The data element indicates the maneuver being made by the motorist at the time of a pedestrian collision.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB35.,9,Unknown Motorist`s Maneuver,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,PEDLEG,pedleg,Leg Intersection,The data element identifies the leg of the intersection where the pedestrian crash occurred.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB36.,1,Near,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,PEDLEG,pedleg,Leg Intersection,The data element identifies the leg of the intersection where the pedestrian crash occurred.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB36.,2,Far,1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,PEDLEG,pedleg,Leg Intersection,The data element identifies the leg of the intersection where the pedestrian crash occurred.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB36.,7,Not a Pedestrian,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDLEG,pedleg,Leg Intersection,The data element identifies the leg of the intersection where the pedestrian crash occurred.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB36.,8,Not Applicable,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDLEG,pedleg,Leg Intersection,The data element identifies the leg of the intersection where the pedestrian crash occurred.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB36.,9,Unknown,1,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,7,Not a Pedestrian,1,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,8,Not Applicable,1,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,0,Not a Pedestrian,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,100,Unusual Circumstances,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,200,Backing Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,310,Working or Playing in Roadway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,340,Bus-Related,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,350,Unique Midblock,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,400,Walking/Running Along Roadway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,460,Driveway Access/Driveway Access Related,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,500,Waiting to Cross,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,600,Pedestrian in Roadway - Circumstances Unknown,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,720,Multiple Threat / Trapped,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,740,Dash / Dart-Out,1,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,750,Crossing Roadway - Vehicle Not Turning,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,790,Crossing Roadway - Vehicle Turning,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,800,Non-Trafficway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,910,Crossing Expressway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,990,Other / Unknown - Insufficient Details,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,0,Not a Cyclist,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,110,Loss of Control / Turning Error,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,140,Motorist Failed to Yield - Sign-Controlled Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,145,Bicyclist Failed to Yield - Sign-Controlled Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,150,Motorist Failed to Yield - Signalized Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,158,Bicyclist Failed to Yield - Signalized Intersection,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,190,Crossing Paths - Other Circumstances,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,210,Motorist Left Turn / Merge,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,215,Motorist Right Turn / Merge,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,219,Parking / Bus-Related,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,220,Bicyclist Left Turn / Merge,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,225,Bicyclist Right Turn / Merge,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,230,Motorist Overtaking Bicyclist,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,240,Bicyclist Overtaking Motorist,1,1,1,1,1,1,1,1,NA,NA
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,258,Wrong-Way / Wrong-Side,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,290,Parallel Paths - Other Circumstances,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,310,Bicyclist Failed to Yield - Midblock,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,320,Motorist Failed to Yield - Midblock,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,600,Backing Vehicle,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,850,Other / Unusual Circumstances,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,910,Non-Trafficway,1,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,990,Other / Unknown - Insufficient Details,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,PER_NO,per_no,Person Number,"This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files.","Each occupant of the vehicle is numbered, and each non-occupant is numbered; in the case of a non-occupant the vehicle number is zero. The numbers for occupants are consecutive for each vehicle beginning with 1. Numbers are never skipped. Drivers do not have to be coded 1. Non- Occupants are identified by vehicle number 0 and are numbered consecutively starting with 1 for each non-motorist. To get drivers see data element PER_TYP under Person Type. PER_NO can be used in merges, e.g., when merging the FARS person data file with the multiple cause of death file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,safetyeq,MSAFEQMT,msafeqmt,Non-Motorist Safety Equipment Use,This data element indicates the safety equipment that was used by this non-motorist involved in the crash.,There can be one or more safety equipment responses for each non-motorist.,1,None Used,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,safetyeq,MSAFEQMT,msafeqmt,Non-Motorist Safety Equipment Use,This data element indicates the safety equipment that was used by this non-motorist involved in the crash.,There can be one or more safety equipment responses for each non-motorist.,2,Helmet,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,safetyeq,MSAFEQMT,msafeqmt,Non-Motorist Safety Equipment Use,This data element indicates the safety equipment that was used by this non-motorist involved in the crash.,There can be one or more safety equipment responses for each non-motorist.,3,"Reflective Equipment/Clothing (jacket, backpack, etc.)",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,safetyeq,MSAFEQMT,msafeqmt,Non-Motorist Safety Equipment Use,This data element indicates the safety equipment that was used by this non-motorist involved in the crash.,There can be one or more safety equipment responses for each non-motorist.,4,"Protective Pads Used(elbows, knees, shins, etc.)",1,NA,NA,NA,NA,NA,NA,NA,NA,NA
FARS,safetyeq,MSAFEQMT,msafeqmt,Non-Motorist Safety Equipment Use,This data element indicates the safety equipment that was used by this non-motorist involved in the crash.,There can be one or more safety equipment responses for each non-motorist.,5,Lighting,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,safetyeq,MSAFEQMT,msafeqmt,Non-Motorist Safety Equipment Use,This data element indicates the safety equipment that was used by this non-motorist involved in the crash.,There can be one or more safety equipment responses for each non-motorist.,7,Other Safety Equipment,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,safetyeq,MSAFEQMT,msafeqmt,Non-Motorist Safety Equipment Use,This data element indicates the safety equipment that was used by this non-motorist involved in the crash.,There can be one or more safety equipment responses for each non-motorist.,8,Not Reported,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,safetyeq,MSAFEQMT,msafeqmt,Non-Motorist Safety Equipment Use,This data element indicates the safety equipment that was used by this non-motorist involved in the crash.,There can be one or more safety equipment responses for each non-motorist.,9,Unknown if Used,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,miper,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,miper,PER_NO,per_no,Person Number,"This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files.","Each occupant of the vehicle is numbered, and each non-occupant is numbered; in the case of a non-occupant the vehicle number is zero. The numbers for occupants are consecutive for each vehicle beginning with 1. Numbers are never skipped. Drivers do not have to be coded 1. Non- Occupants are identified by vehicle number 0 and are numbered consecutively starting with 1 for each non-motorist. To get drivers see data element PER_TYP under Person Type. PER_NO can be used in merges, e.g., when merging the FARS person data file with the multiple cause of death file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,miper,P1,p1,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,miper,P2,p2,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,miper,P3,p3,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,miper,P4,p4,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,miper,P5,p5,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,miper,P6,p6,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,miper,P7,p7,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,miper,P8,p8,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,miper,P9,p9,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,miper,P10,p10,Imputed BAC Value,NA,NA,NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,PER_NO,per_no,Person Number,"This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files.","Each occupant of the vehicle is numbered, and each non-occupant is numbered; in the case of a non-occupant the vehicle number is zero. The numbers for occupants are consecutive for each vehicle beginning with 1. Numbers are never skipped. Drivers do not have to be coded 1. Non- Occupants are identified by vehicle number 0 and are numbered consecutively starting with 1 for each non-motorist. To get drivers see data element PER_TYP under Person Type. PER_NO can be used in merges, e.g., when merging the FARS person data file with the multiple cause of death file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",0,None Noted,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",1,Dart-Out,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",2,Failure to Yield Right-Of-Way,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",3,"Failure to Obey Traffic Signs, Signals or Officer",1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",4,"In Roadway Improperly (Standing, Lying, Working, Playing, etc.)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",5,Entering/Exiting Parked or Stopped Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",6,"Inattentive (Talking, Eating, Etc.)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",7,Improper Turn/Merge,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",8,Improper Passing,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",9,Wrong-Way Riding or Walking,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",10,Riding on Wrong Side of Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",11,Dash,1,1,1,1,1,NA,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",12,Improper Crossing of Roadway or Intersection (Jaywalking),1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",13,Failing to Have Lights on When Required,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",14,Operating Without Required Equipment,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",15,Improper or Erratic Lane Changing,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",16,Failure to Keep in Proper Lane or Running Off Road,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",17,Making Improper Entry to or Exit From Trafficway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",18,"Operating in other Erratic, Reckless, Careless or Negligent Manner",1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",19,"Not Visible (Dark clothing, No Lighting, etc.)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",20,Passing with Insufficient Distance or Inadequate Visibility or Failing to Yield to Overtaking Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",21,Other (Specify:),1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,PER_NO,per_no,Person Number,"This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files.","Each occupant of the vehicle is numbered, and each non-occupant is numbered; in the case of a non-occupant the vehicle number is zero. The numbers for occupants are consecutive for each vehicle beginning with 1. Numbers are never skipped. Drivers do not have to be coded 1. Non- Occupants are identified by vehicle number 0 and are numbered consecutively starting with 1 for each non-motorist. To get drivers see data element PER_TYP under Person Type. PER_NO can be used in merges, e.g., when merging the FARS person data file with the multiple cause of death file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",0,None/Apparently Normal,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",1,"Ill, Blackout",1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",2,Asleep or Fatigued,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",3,"Walking with a Cane or Crutches, etc.",1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",4,Paraplegic Or Restricted To A Wheelchair,1,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",5,Impaired Due to Previous Injury,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",6,Deaf,1,1,1,1,1,1,1,NA,NA,NA
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",7,Blind,1,1,1,1,1,1,1,NA,NA,NA
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",8,"Emotional (depressed, angry, disturbed, etc)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",9,"Under the Influence of Alcohol, Drugs or Medication",1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",10,Physical Impairment - No Details,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",96,Other Physical Impairment,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",98,Not Reported,1,1,1,1,1,1,1,1,1,1
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",99,Unknown if Impaired,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,1,1,1,1,1,1,1,1,1,1
FARS,nmprior,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,nmprior,PER_NO,per_no,Person Number,"This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files.","Each occupant of the vehicle is numbered, and each non-occupant is numbered; in the case of a non-occupant the vehicle number is zero. The numbers for occupants are consecutive for each vehicle beginning with 1. Numbers are never skipped. Drivers do not have to be coded 1. Non- Occupants are identified by vehicle number 0 and are numbered consecutively starting with 1 for each non-motorist. To get drivers see data element PER_TYP under Person Type. PER_NO can be used in merges, e.g., when merging the FARS person data file with the multiple cause of death file.",NA,(Self-evident),1,1,1,1,1,1,1,1,1,1
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",1,Going To or From School (K-12),1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",2,Waiting to Cross Roadway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",3,Crossing Roadway,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",4,Jogging/Running,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",5,Movement Along Roadway with Traffic (In or Adjacent to Travel Lane),1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",6,Movement Along Roadway Against Traffic (In or Adjacent to Travel Lane),1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",8,"In Roadway - Other (Working, Playing, Etc.)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",9,"Adjacent to Roadway (e.g., Shoulder, Median)",1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",10,Working in Trafficway (Incident Response),1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",11,Entering / Exiting Parked or Stopped Vehicle,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",12,"Disabled Vehicle Related (Working on, Pushing, Leaving/Approaching)",1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",14,Other (Specify:),1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",16,Movement Along Roadway - Direction Unknown,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",98,Not Reported,1,1,1,1,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",99,Unknown,1,1,1,1,NA,NA,NA,NA,NA,NA
FARS,accident,RUR_URB,rur_urb,Land Use,This data element identifies the classification of the segment of the trafficway on which the crash occurred based on FHWA-approved adjusted Census boundaries of small urban and urbanized areas.,From 1975 to 1986 there was a similar Land Use (LAND_USE) data element. From 1987 to 2014 urban and rural classifications can be obtained from the data element Roadway Function Class. Prior to 2023 this data element’s name was “Land Use.”,1,Rural,NA,1,1,1,1,1,1,1,1,NA
FARS,accident,RUR_URB,rur_urb,Land Use,This data element identifies the classification of the segment of the trafficway on which the crash occurred based on FHWA-approved adjusted Census boundaries of small urban and urbanized areas.,From 1975 to 1986 there was a similar Land Use (LAND_USE) data element. From 1987 to 2014 urban and rural classifications can be obtained from the data element Roadway Function Class. Prior to 2023 this data element’s name was “Land Use.”,2,Urban,NA,1,1,1,1,1,1,1,1,NA
FARS,accident,RUR_URB,rur_urb,Land Use,This data element identifies the classification of the segment of the trafficway on which the crash occurred based on FHWA-approved adjusted Census boundaries of small urban and urbanized areas.,From 1975 to 1986 there was a similar Land Use (LAND_USE) data element. From 1987 to 2014 urban and rural classifications can be obtained from the data element Roadway Function Class. Prior to 2023 this data element’s name was “Land Use.”,6,Trafficway Not in State Inventory,NA,1,1,1,1,1,1,1,1,NA
FARS,accident,RUR_URB,rur_urb,Land Use,This data element identifies the classification of the segment of the trafficway on which the crash occurred based on FHWA-approved adjusted Census boundaries of small urban and urbanized areas.,From 1975 to 1986 there was a similar Land Use (LAND_USE) data element. From 1987 to 2014 urban and rural classifications can be obtained from the data element Roadway Function Class. Prior to 2023 this data element’s name was “Land Use.”,8,Not Reported,NA,1,1,1,1,1,1,1,1,NA
FARS,accident,RUR_URB,rur_urb,Land Use,This data element identifies the classification of the segment of the trafficway on which the crash occurred based on FHWA-approved adjusted Census boundaries of small urban and urbanized areas.,From 1975 to 1986 there was a similar Land Use (LAND_USE) data element. From 1987 to 2014 urban and rural classifications can be obtained from the data element Roadway Function Class. Prior to 2023 this data element’s name was “Land Use.”,9,Unknown,NA,1,1,1,1,1,1,1,1,NA
FARS,accident,FUNC_SYS,func_sys,Functional System,NA,NA,1,Interstate,NA,1,1,1,1,1,1,1,1,1
FARS,accident,FUNC_SYS,func_sys,Functional System,NA,NA,2,Principal Arterial - Other Freeways and Expressways,NA,1,1,1,1,1,1,1,1,NA
FARS,accident,FUNC_SYS,func_sys,Functional System,NA,NA,3,Principal Arterial - Other,NA,1,1,1,1,1,1,1,1,NA
FARS,accident,FUNC_SYS,func_sys,Functional System,NA,NA,4,Minor Arterial,NA,1,1,1,1,1,1,1,1,1
FARS,accident,FUNC_SYS,func_sys,Functional System,NA,NA,5,Major Collector,NA,1,1,1,1,1,1,1,1,1
FARS,accident,FUNC_SYS,func_sys,Functional System,NA,NA,6,Minor Collector,NA,1,1,1,1,1,1,1,1,1
FARS,accident,FUNC_SYS,func_sys,Functional System,NA,NA,7,Local,NA,1,1,1,1,1,1,1,1,1
FARS,accident,FUNC_SYS,func_sys,Functional System,NA,NA,96,Trafficway Not in State Inventory,NA,1,1,1,1,1,1,1,1,1
FARS,accident,FUNC_SYS,func_sys,Functional System,NA,NA,98,Not Reported,NA,1,1,1,1,1,1,1,1,1
FARS,accident,FUNC_SYS,func_sys,Functional System,NA,NA,99,Unknown,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,1,State Highway Agency,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,2,County Highway Agency,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,3,Town or Township Highway Agency,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,4,City or Municipal Highway Agency,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,11,"State Park, Forest, or Reservation Agency",NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,12,"Local Park, Forest or Reservation Agency",NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,21,Other State Agency,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,25,Other Local Agency,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,26,Private (other than Railroad),NA,1,1,1,1,1,1,1,1,NA
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,27,Railroad,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,31,State Toll Road,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,32,Local Toll Authority,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,40,"Other Public Instrumentality (i.e., Airport)",NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,50,Indian Tribe Nation,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,60,Other Federal Agency,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,62,Bureau of Indian Affairs,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,63,Bureau of Fish and Wildlife,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,64,U.S. Forest Service,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,66,National Park Service,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,67,Tennessee Valley Authority,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,68,Bureau of Land Management,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,69,Bureau of Reclamation,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,70,Corps of Engineers,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,72,Air Force,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,74,Navy/Marines,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,80,Army,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,96,Trafficway Not in State Inventory,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,98,Not Reported,NA,1,1,1,1,1,1,1,1,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,99,Unknown,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2422,Jeep / Kaiser-Jeep / Willys- Jeep Grand Cherokee (For 2014 on.  Use model 404 for model years prior to 2013.),NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6019,Chrysler 100,NA,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13017,Lincoln Continental,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18026,Buick / Opel Cascada,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18405,Buick / Opel Envision,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19026,Cadillac CT6,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19401,Cadillac XT5,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20445,Chevrolet City Express,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34044,"BMW X6 (For 2008-2015. For 2016 on, see model 404.)",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34404,"BMW X6 (For 2016 on. For 2008-2015, see model 044.)",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36039,Fiat 124 Spider,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36402,Fiat 500X,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37404,Honda HR-V,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39039,Jaguar XE,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39401,Jaguar F-Pace,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39999,Jaguar Unknown (JAGUAR),NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41056,Mazda CX-3,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42056,Mercedes-Benz AMG GT S,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42404,Mercedes-Benz GLE Class,NA,1,1,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42405,Mercedes-Benz GLC Class,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42462,Mercedes-Benz Metris,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49055,Toyota Mirai,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51983,"Volvo Bus : Rear engine, Flat front",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54043,Acura NSX (2016 on.  For 1991-2005 see model 033.),NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58045,Infiniti Q40,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58046,Infiniti Q30,NA,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59035,Lexus IS-250/300/350/500/200t,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59403,Lexus RX330/350/400h/450h,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67036,Scion iA,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67037,Scion iM,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_HGT,dr_hgt,Driver Height,This data element identifies this driver’s height (in inches).,"This information was coded in two subfields that are in feet or in inches. If both the Driver Height in feet and Driver Height in inches are known, then we do the conversion using (Feet)*12 + inches; if feet are unknown or if inches are 98 (Other) or 99 (Unknown) then DR_HGT=999 (Unknown). Minimum height 2 feet = 24 inches, maximum height 8 feet 11 inches = 107 inches. In 2009, if feet and/or inches are unknown (9,99) or blank, then the Driver Height is left blank. However, in 2010 if feet and/or inches are unknown (9,99) then the Driver Height is computed as 999 (Unknown). The Driver Presence data element is not taken into account. In 2011, if feet and/or inches are unknown (9,99) and Driver Presence is 1, then the Driver Height is computed as 999 (Unknown) otherwise Driver Height is computed as 998 (No Driver Present/Unknown if Driver Present).",998,Other,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,DR_HGT,dr_hgt,Driver Height,This data element identifies this driver’s height (in inches).,"This information was coded in two subfields that are in feet or in inches. If both the Driver Height in feet and Driver Height in inches are known, then we do the conversion using (Feet)*12 + inches; if feet are unknown or if inches are 98 (Other) or 99 (Unknown) then DR_HGT=999 (Unknown). Minimum height 2 feet = 24 inches, maximum height 8 feet 11 inches = 107 inches. In 2009, if feet and/or inches are unknown (9,99) or blank, then the Driver Height is left blank. However, in 2010 if feet and/or inches are unknown (9,99) then the Driver Height is computed as 999 (Unknown). The Driver Presence data element is not taken into account. In 2011, if feet and/or inches are unknown (9,99) and Driver Presence is 1, then the Driver Height is computed as 999 (Unknown) otherwise Driver Height is computed as 998 (No Driver Present/Unknown if Driver Present).",999,Unknown,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",0,None,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",1,1,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",2,2,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",3,3,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",4,4,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",5,5,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",6,6,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",7,7,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",8,8,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",9,9,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",10,10,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",11,11,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",12,12,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",13,13,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",14,14,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",15,15,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",16,16,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",17,17,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",18,18,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",19,19,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",20,20,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",21,21,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",22,22,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",23,23,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",24,24,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",25,25,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",26,26,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",27,27,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",28,28,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",29,29,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",30,30,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",31,31,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",32,32,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",33,33,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",34,34,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",35,35,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",36,36,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",37,37,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",38,38,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",39,39,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",40,40,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",41,41,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",42,42,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",43,43,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",44,44,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",45,45,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",46,46,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",47,47,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",48,48,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",49,49,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",50,50,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",51,51,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",52,52,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",53,53,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",54,54,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",55,55,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",56,56,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",57,57,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",58,58,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",59,59,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",60,60,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",61,61,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",62,62,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",63,63,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",64,64,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",65,65,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",66,66,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",67,67,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",68,68,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",69,69,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",70,70,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",71,71,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",72,72,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",73,73,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",74,74,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",75,75,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",76,76,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",77,77,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",78,78,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",79,79,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",80,80,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",81,81,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",82,82,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",83,83,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",84,84,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",85,85,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",86,86,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",87,87,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",88,88,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",89,89,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",90,90,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",91,91,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",92,92,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",93,93,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",94,94,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",95,95,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",96,96,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",97,97,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",99,Unknown,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,PREV_OTH,prev_oth,Previous Other Moving Violation Convictions,This data element records any other previous moving violations or convictions for this driver that occurred within 5 years of the crash date.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",998,No Driver Present/Unknown if Driver Present,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2015,2015,NA,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2015,2015,NA,1,1,1,1,1,1,1,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,28,Improper Lane Usage,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,33,"Passing where Prohibited by Posted Signs, Pavement Markings or School Bus Displaying Warning not to Pass",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,34,Passing on Right Side,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,36,"Operating the Vehicle in an Erratic, Reckless or Negligent Manner.",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,59,Getting Off/Out of a Vehicle,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,28,Improper Lane Usage,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,33,"Passing where Prohibited by Posted Signs, Pavement Markings or School Bus Displaying Warning not to Pass",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,34,Passing on Right Side,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,36,"Operating the Vehicle in an Erratic, Reckless or Negligent Manner.",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,59,Getting Off/Out of a Vehicle,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,28,Improper Lane Usage,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,33,"Passing where Prohibited by Posted Signs, Pavement Markings or School Bus Displaying Warning not to Pass",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,34,Passing on Right Side,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,36,"Operating the Vehicle in an Erratic, Reckless or Negligent Manner.",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,59,Getting Off/Out of a Vehicle,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,28,Improper Lane Usage,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,33,"Passing where Prohibited by Posted Signs, Pavement Markings or School Bus Displaying Warning not to Pass",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,34,Passing on Right Side,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,36,"Operating the Vehicle in an Erratic, Reckless or Negligent Manner.",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,59,Getting Off/Out of a Vehicle,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,85,85 MPH,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,90,90 MPH,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,95,95 MPH,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,51,Traveling in same direction with lower steady speed,NA,1,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,92,Backing Veh.,NA,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,person,EJ_PATH,ej_path,Ejection Path,This data element identifies the path by which this person was ejected from the vehicle.,NA,0,Ejection Path Not Applicable,NA,1,1,1,1,1,1,1,1,1
FARS,person,EJ_PATH,ej_path,Ejection Path,This data element identifies the path by which this person was ejected from the vehicle.,NA,9,Ejection Path Unknown,NA,1,1,1,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,2,Breath Test (AC),NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,0,0.000 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,1,0.001 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,2,0.002 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,3,0.003 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,4,0.004 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,5,0.005 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,6,0.006 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,7,0.007 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,8,0.008 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,9,0.009 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,10,0.010 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,11,0.011 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,12,0.012 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,13,0.013 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,14,0.014 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,15,0.015 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,16,0.016 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,17,0.017 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,18,0.018 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,19,0.019 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,20,0.020 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,21,0.021 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,22,0.022 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,23,0.023 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,24,0.024 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,25,0.025 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,26,0.026 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,27,0.027 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,28,0.028 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,29,0.029 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,30,0.030 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,31,0.031 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,32,0.032 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,33,0.033 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,34,0.034 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,35,0.035 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,36,0.036 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,37,0.037 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,38,0.038 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,39,0.039 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,40,0.040 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,41,0.041 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,42,0.042 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,43,0.043 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,44,0.044 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,45,0.045 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,46,0.046 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,47,0.047 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,48,0.048 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,49,0.049 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,50,0.050 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,51,0.051 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,52,0.052 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,53,0.053 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,54,0.054 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,55,0.055 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,56,0.056 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,57,0.057 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,58,0.058 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,59,0.059 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,60,0.060 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,61,0.061 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,62,0.062 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,63,0.063 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,64,0.064 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,65,0.065 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,66,0.066 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,67,0.067 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,68,0.068 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,69,0.069 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,70,0.070 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,71,0.071 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,72,0.072 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,73,0.073 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,74,0.074 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,75,0.075 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,76,0.076 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,77,0.077 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,78,0.078 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,79,0.079 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,80,0.080 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,81,0.081 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,82,0.082 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,83,0.083 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,84,0.084 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,85,0.085 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,86,0.086 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,87,0.087 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,88,0.088 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,89,0.089 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,90,0.090 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,91,0.091 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,92,0.092 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,93,0.093 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,94,0.094 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,95,0.095 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,96,0.096 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,97,0.097 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,98,0.098 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,99,0.099 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,100,0.100 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,101,0.101 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,102,0.102 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,103,0.103 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,104,0.104 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,105,0.105 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,106,0.106 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,107,0.107 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,108,0.108 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,109,0.109 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,110,0.110 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,111,0.111 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,112,0.112 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,113,0.113 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,114,0.114 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,115,0.115 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,116,0.116 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,117,0.117 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,118,0.118 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,119,0.119 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,120,0.120 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,121,0.121 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,122,0.122 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,123,0.123 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,124,0.124 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,125,0.125 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,126,0.126 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,127,0.127 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,128,0.128 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,129,0.129 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,130,0.130 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,131,0.131 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,132,0.132 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,133,0.133 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,134,0.134 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,135,0.135 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,136,0.136 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,137,0.137 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,138,0.138 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,139,0.139 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,140,0.140 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,141,0.141 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,142,0.142 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,143,0.143 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,144,0.144 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,145,0.145 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,146,0.146 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,147,0.147 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,148,0.148 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,149,0.149 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,150,0.150 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,151,0.151 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,152,0.152 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,153,0.153 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,154,0.154 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,155,0.155 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,156,0.156 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,157,0.157 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,158,0.158 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,159,0.159 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,160,0.160 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,161,0.161 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,162,0.162 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,163,0.163 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,164,0.164 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,165,0.165 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,166,0.166 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,167,0.167 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,168,0.168 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,169,0.169 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,170,0.170 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,171,0.171 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,172,0.172 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,173,0.173 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,174,0.174 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,175,0.175 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,176,0.176 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,177,0.177 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,178,0.178 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,179,0.179 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,180,0.180 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,181,0.181 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,182,0.182 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,183,0.183 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,184,0.184 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,185,0.185 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,186,0.186 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,187,0.187 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,188,0.188 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,189,0.189 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,190,0.190 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,191,0.191 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,192,0.192 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,193,0.193 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,194,0.194 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,195,0.195 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,196,0.196 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,197,0.197 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,198,0.198 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,199,0.199 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,200,0.200 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,201,0.201 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,202,0.202 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,203,0.203 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,204,0.204 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,205,0.205 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,206,0.206 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,207,0.207 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,208,0.208 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,209,0.209 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,210,0.210 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,211,0.211 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,212,0.212 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,213,0.213 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,214,0.214 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,215,0.215 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,216,0.216 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,217,0.217 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,218,0.218 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,219,0.219 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,220,0.220 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,221,0.221 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,222,0.222 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,223,0.223 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,224,0.224 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,225,0.225 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,226,0.226 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,227,0.227 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,228,0.228 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,229,0.229 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,230,0.230 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,231,0.231 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,232,0.232 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,233,0.233 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,234,0.234 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,235,0.235 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,236,0.236 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,237,0.237 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,238,0.238 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,239,0.239 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,240,0.240 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,241,0.241 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,242,0.242 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,243,0.243 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,244,0.244 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,245,0.245 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,246,0.246 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,247,0.247 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,248,0.248 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,249,0.249 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,250,0.250 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,251,0.251 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,252,0.252 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,253,0.253 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,254,0.254 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,255,0.255 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,256,0.256 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,257,0.257 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,258,0.258 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,259,0.259 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,260,0.260 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,261,0.261 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,262,0.262 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,263,0.263 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,264,0.264 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,265,0.265 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,266,0.266 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,267,0.267 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,268,0.268 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,269,0.269 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,270,0.270 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,271,0.271 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,272,0.272 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,273,0.273 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,274,0.274 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,275,0.275 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,276,0.276 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,277,0.277 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,278,0.278 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,279,0.279 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,280,0.280 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,281,0.281 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,282,0.282 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,283,0.283 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,284,0.284 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,285,0.285 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,286,0.286 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,287,0.287 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,288,0.288 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,289,0.289 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,290,0.290 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,291,0.291 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,292,0.292 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,293,0.293 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,294,0.294 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,295,0.295 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,296,0.296 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,297,0.297 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,298,0.298 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,299,0.299 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,300,0.300 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,301,0.301 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,302,0.302 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,303,0.303 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,304,0.304 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,305,0.305 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,306,0.306 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,307,0.307 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,308,0.308 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,309,0.309 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,310,0.310 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,311,0.311 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,312,0.312 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,313,0.313 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,314,0.314 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,315,0.315 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,316,0.316 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,317,0.317 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,318,0.318 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,319,0.319 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,320,0.320 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,321,0.321 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,322,0.322 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,323,0.323 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,324,0.324 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,325,0.325 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,326,0.326 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,327,0.327 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,328,0.328 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,329,0.329 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,330,0.330 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,331,0.331 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,332,0.332 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,333,0.333 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,334,0.334 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,335,0.335 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,336,0.336 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,337,0.337 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,338,0.338 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,339,0.339 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,340,0.340 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,341,0.341 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,342,0.342 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,343,0.343 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,344,0.344 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,345,0.345 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,346,0.346 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,347,0.347 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,348,0.348 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,349,0.349 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,350,0.350 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,351,0.351 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,352,0.352 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,353,0.353 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,354,0.354 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,355,0.355 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,356,0.356 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,357,0.357 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,358,0.358 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,359,0.359 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,360,0.360 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,361,0.361 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,362,0.362 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,363,0.363 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,364,0.364 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,365,0.365 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,366,0.366 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,367,0.367 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,368,0.368 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,369,0.369 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,370,0.370 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,371,0.371 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,372,0.372 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,373,0.373 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,374,0.374 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,375,0.375 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,376,0.376 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,377,0.377 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,378,0.378 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,379,0.379 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,380,0.380 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,381,0.381 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,382,0.382 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,383,0.383 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,384,0.384 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,385,0.385 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,386,0.386 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,387,0.387 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,388,0.388 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,389,0.389 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,390,0.390 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,391,0.391 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,392,0.392 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,393,0.393 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,394,0.394 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,395,0.395 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,396,0.396 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,397,0.397 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,398,0.398 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,399,0.399 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,400,0.400 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,401,0.401 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,402,0.402 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,403,0.403 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,404,0.404 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,405,0.405 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,406,0.406 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,407,0.407 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,408,0.408 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,409,0.409 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,410,0.410 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,411,0.411 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,412,0.412 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,413,0.413 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,414,0.414 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,415,0.415 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,416,0.416 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,417,0.417 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,418,0.418 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,419,0.419 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,420,0.420 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,421,0.421 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,422,0.422 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,423,0.423 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,424,0.424 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,425,0.425 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,426,0.426 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,427,0.427 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,428,0.428 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,429,0.429 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,430,0.430 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,431,0.431 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,432,0.432 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,433,0.433 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,434,0.434 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,435,0.435 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,436,0.436 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,437,0.437 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,438,0.438 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,439,0.439 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,440,0.440 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,441,0.441 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,442,0.442 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,443,0.443 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,444,0.444 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,445,0.445 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,446,0.446 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,447,0.447 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,448,0.448 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,449,0.449 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,450,0.450 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,451,0.451 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,452,0.452 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,453,0.453 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,454,0.454 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,455,0.455 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,456,0.456 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,457,0.457 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,458,0.458 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,459,0.459 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,460,0.460 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,461,0.461 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,462,0.462 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,463,0.463 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,464,0.464 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,465,0.465 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,466,0.466 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,467,0.467 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,468,0.468 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,469,0.469 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,470,0.470 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,471,0.471 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,472,0.472 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,473,0.473 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,474,0.474 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,475,0.475 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,476,0.476 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,477,0.477 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,478,0.478 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,479,0.479 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,480,0.480 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,481,0.481 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,482,0.482 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,483,0.483 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,484,0.484 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,485,0.485 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,486,0.486 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,487,0.487 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,488,0.488 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,489,0.489 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,490,0.490 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,491,0.491 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,492,0.492 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,493,0.493 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,494,0.494 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,495,0.495 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,496,0.496 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,497,0.497 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,498,0.498 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,499,0.499 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,500,0.500 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,501,0.501 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,502,0.502 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,503,0.503 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,504,0.504 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,505,0.505 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,506,0.506 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,507,0.507 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,508,0.508 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,509,0.509 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,510,0.510 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,511,0.511 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,512,0.512 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,513,0.513 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,514,0.514 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,515,0.515 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,516,0.516 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,517,0.517 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,518,0.518 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,519,0.519 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,520,0.520 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,521,0.521 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,522,0.522 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,523,0.523 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,524,0.524 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,525,0.525 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,526,0.526 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,527,0.527 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,528,0.528 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,529,0.529 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,530,0.530 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,531,0.531 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,532,0.532 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,533,0.533 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,534,0.534 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,535,0.535 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,536,0.536 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,537,0.537 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,538,0.538 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,539,0.539 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,540,0.540 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,541,0.541 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,542,0.542 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,543,0.543 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,544,0.544 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,545,0.545 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,546,0.546 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,547,0.547 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,548,0.548 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,549,0.549 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,550,0.550 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,551,0.551 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,552,0.552 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,553,0.553 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,554,0.554 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,555,0.555 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,556,0.556 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,557,0.557 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,558,0.558 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,559,0.559 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,560,0.560 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,561,0.561 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,562,0.562 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,563,0.563 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,564,0.564 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,565,0.565 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,566,0.566 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,567,0.567 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,568,0.568 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,569,0.569 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,570,0.570 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,571,0.571 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,572,0.572 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,573,0.573 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,574,0.574 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,575,0.575 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,576,0.576 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,577,0.577 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,578,0.578 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,579,0.579 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,580,0.580 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,581,0.581 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,582,0.582 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,583,0.583 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,584,0.584 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,585,0.585 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,586,0.586 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,587,0.587 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,588,0.588 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,589,0.589 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,590,0.590 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,591,0.591 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,592,0.592 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,593,0.593 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,594,0.594 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,595,0.595 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,596,0.596 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,597,0.597 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,598,0.598 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,599,0.599 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,600,0.600 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,601,0.601 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,602,0.602 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,603,0.603 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,604,0.604 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,605,0.605 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,606,0.606 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,607,0.607 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,608,0.608 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,609,0.609 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,610,0.610 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,611,0.611 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,612,0.612 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,613,0.613 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,614,0.614 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,615,0.615 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,616,0.616 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,617,0.617 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,618,0.618 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,619,0.619 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,620,0.620 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,621,0.621 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,622,0.622 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,623,0.623 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,624,0.624 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,625,0.625 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,626,0.626 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,627,0.627 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,628,0.628 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,629,0.629 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,630,0.630 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,631,0.631 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,632,0.632 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,633,0.633 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,634,0.634 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,635,0.635 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,636,0.636 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,637,0.637 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,638,0.638 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,639,0.639 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,640,0.640 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,641,0.641 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,642,0.642 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,643,0.643 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,644,0.644 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,645,0.645 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,646,0.646 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,647,0.647 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,648,0.648 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,649,0.649 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,650,0.650 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,651,0.651 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,652,0.652 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,653,0.653 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,654,0.654 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,655,0.655 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,656,0.656 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,657,0.657 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,658,0.658 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,659,0.659 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,660,0.660 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,661,0.661 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,662,0.662 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,663,0.663 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,664,0.664 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,665,0.665 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,666,0.666 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,667,0.667 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,668,0.668 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,669,0.669 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,670,0.670 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,671,0.671 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,672,0.672 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,673,0.673 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,674,0.674 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,675,0.675 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,676,0.676 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,677,0.677 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,678,0.678 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,679,0.679 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,680,0.680 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,681,0.681 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,682,0.682 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,683,0.683 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,684,0.684 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,685,0.685 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,686,0.686 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,687,0.687 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,688,0.688 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,689,0.689 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,690,0.690 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,691,0.691 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,692,0.692 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,693,0.693 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,694,0.694 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,695,0.695 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,696,0.696 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,697,0.697 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,698,0.698 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,699,0.699 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,700,0.700 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,701,0.701 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,702,0.702 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,703,0.703 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,704,0.704 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,705,0.705 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,706,0.706 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,707,0.707 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,708,0.708 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,709,0.709 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,710,0.710 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,711,0.711 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,712,0.712 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,713,0.713 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,714,0.714 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,715,0.715 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,716,0.716 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,717,0.717 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,718,0.718 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,719,0.719 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,720,0.720 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,721,0.721 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,722,0.722 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,723,0.723 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,724,0.724 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,725,0.725 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,726,0.726 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,727,0.727 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,728,0.728 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,729,0.729 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,730,0.730 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,731,0.731 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,732,0.732 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,733,0.733 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,734,0.734 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,735,0.735 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,736,0.736 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,737,0.737 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,738,0.738 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,739,0.739 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,740,0.740 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,741,0.741 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,742,0.742 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,743,0.743 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,744,0.744 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,745,0.745 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,746,0.746 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,747,0.747 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,748,0.748 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,749,0.749 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,750,0.750 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,751,0.751 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,752,0.752 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,753,0.753 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,754,0.754 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,755,0.755 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,756,0.756 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,757,0.757 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,758,0.758 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,759,0.759 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,760,0.760 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,761,0.761 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,762,0.762 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,763,0.763 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,764,0.764 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,765,0.765 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,766,0.766 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,767,0.767 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,768,0.768 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,769,0.769 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,770,0.770 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,771,0.771 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,772,0.772 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,773,0.773 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,774,0.774 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,775,0.775 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,776,0.776 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,777,0.777 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,778,0.778 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,779,0.779 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,780,0.780 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,781,0.781 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,782,0.782 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,783,0.783 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,784,0.784 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,785,0.785 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,786,0.786 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,787,0.787 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,788,0.788 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,789,0.789 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,790,0.790 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,791,0.791 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,792,0.792 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,793,0.793 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,794,0.794 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,795,0.795 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,796,0.796 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,797,0.797 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,798,0.798 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,799,0.799 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,800,0.800 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,801,0.801 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,802,0.802 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,803,0.803 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,804,0.804 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,805,0.805 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,806,0.806 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,807,0.807 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,808,0.808 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,809,0.809 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,810,0.810 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,811,0.811 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,812,0.812 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,813,0.813 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,814,0.814 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,815,0.815 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,816,0.816 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,817,0.817 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,818,0.818 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,819,0.819 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,820,0.820 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,821,0.821 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,822,0.822 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,823,0.823 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,824,0.824 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,825,0.825 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,826,0.826 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,827,0.827 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,828,0.828 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,829,0.829 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,830,0.830 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,831,0.831 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,832,0.832 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,833,0.833 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,834,0.834 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,835,0.835 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,836,0.836 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,837,0.837 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,838,0.838 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,839,0.839 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,840,0.840 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,841,0.841 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,842,0.842 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,843,0.843 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,844,0.844 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,845,0.845 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,846,0.846 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,847,0.847 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,848,0.848 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,849,0.849 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,850,0.850 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,851,0.851 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,852,0.852 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,853,0.853 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,854,0.854 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,855,0.855 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,856,0.856 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,857,0.857 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,858,0.858 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,859,0.859 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,860,0.860 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,861,0.861 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,862,0.862 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,863,0.863 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,864,0.864 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,865,0.865 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,866,0.866 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,867,0.867 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,868,0.868 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,869,0.869 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,870,0.870 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,871,0.871 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,872,0.872 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,873,0.873 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,874,0.874 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,875,0.875 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,876,0.876 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,877,0.877 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,878,0.878 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,879,0.879 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,880,0.880 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,881,0.881 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,882,0.882 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,883,0.883 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,884,0.884 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,885,0.885 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,886,0.886 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,887,0.887 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,888,0.888 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,889,0.889 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,890,0.890 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,891,0.891 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,892,0.892 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,893,0.893 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,894,0.894 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,895,0.895 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,896,0.896 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,897,0.897 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,898,0.898 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,899,0.899 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,900,0.900 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,901,0.901 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,902,0.902 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,903,0.903 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,904,0.904 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,905,0.905 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,906,0.906 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,907,0.907 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,908,0.908 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,909,0.909 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,910,0.910 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,911,0.911 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,912,0.912 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,913,0.913 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,914,0.914 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,915,0.915 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,916,0.916 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,917,0.917 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,918,0.918 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,919,0.919 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,920,0.920 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,921,0.921 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,922,0.922 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,923,0.923 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,924,0.924 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,925,0.925 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,926,0.926 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,927,0.927 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,928,0.928 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,929,0.929 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,930,0.930 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,931,0.931 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,932,0.932 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,933,0.933 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,934,0.934 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,935,0.935 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,936,0.936 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,937,0.937 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,938,0.938 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,939,0.939 % BAC,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,940,.94 % or Greater,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,995,Not Reported,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,996,Test Not Given,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,997,"AC Test Performed, Results Unknown",NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,998,Positive Reading with No Actual Value,NA,1,1,1,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,999,Unknown if Tested,NA,1,1,1,NA,NA,NA,NA,NA,NA
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2016,2016,NA,1,1,1,1,1,1,1,1,1
FARS,person,LAG_HRS,lag_hrs,Crash to Death Time (Hours),This data element records the hours between the time of the crash and this person’s time of death.,This is a computed data element.,999,Unknown,NA,1,1,1,1,1,1,1,1,1
FARS,person,LAG_MINS,lag_mins,Crash to Death Minutes (Minutes),"This data element records the minutes, in addition to hours (“Lag Hours”), between the time of the crash and this person’s time of death.",This is a computed data element.,99,Unknown,NA,1,1,1,1,1,1,1,1,1
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",28,Improper Lane Usage,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",29,"Intentional Illegal Driving on Road Shoulder, in Ditch, on Sidewalk or on Median",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",33,"Passing where Prohibited by Posted Signs, Pavement Markings or School Bus Displaying Warning not to Pass",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",82,"Pedestrian, Pedal Cyclist or Other Non-Motorist",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",28,Improper Lane Usage,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",29,"Intentional Illegal Driving on Road Shoulder, in Ditch, on Sidewalk or on Median",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",33,"Passing where Prohibited by Posted Signs, Pavement Markings or School Bus Displaying Warning not to Pass",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",82,"Pedestrian, Pedal Cyclist or Other Non-Motorist",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",28,Improper Lane Usage,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",29,"Intentional Illegal Driving on Road Shoulder, in Ditch, on Sidewalk or on Median",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",33,"Passing where Prohibited by Posted Signs, Pavement Markings or School Bus Displaying Warning not to Pass",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",82,"Pedestrian, Pedal Cyclist or Other Non-Motorist",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,violatn,MVIOLATN,mviolatn,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,10,Use of Telecommunications Device,NA,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDLOC,pedloc,Pedestrian Crash Location,This data element identifies where the pedestrian crash occurred with respect to an intersection.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB31.,9,Unknown / Insufficient Information,NA,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKELOC,bikeloc,Bicyclist Crash Location,This data element identifies where the bicyclist crash occurred with respect to an intersection.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB31B.,9,Unknown / Insufficient Information,NA,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDPOS,pedpos,Pedestrian Position,This data element identifies the position/location of the pedestrian with respect to the trafficway when contacted.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB32.,2,Crosswalk Area,NA,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDPOS,pedpos,Pedestrian Position,This data element identifies the position/location of the pedestrian with respect to the trafficway when contacted.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB32.,3,Travel Lane,NA,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDPOS,pedpos,Pedestrian Position,This data element identifies the position/location of the pedestrian with respect to the trafficway when contacted.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB32.,6,Unpaved Right-of-Way,NA,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKEPOS,bikepos,Bicyclist Position,This data element identifies the position/location of the bicyclist with respect to the trafficway when contacted.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB32B.,1,Travel Lane,NA,1,1,1,1,1,1,1,1,1
FARS,pbtype,BIKEPOS,bikepos,Bicyclist Position,This data element identifies the position/location of the bicyclist with respect to the trafficway when contacted.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB32B.,8,Other,NA,1,1,1,1,1,1,1,1,1
FARS,pbtype,MOTMAN,motman,Motorist Maneuver,This data element identifies if the motorist was engaged in a turning maneuver at an intersection prior to being involved in a pedestrian crash. The data element indicates the maneuver being made by the motorist at the time of a pedestrian collision.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB35.,9,Unknown Motorist Maneuver,NA,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDLEG,pedleg,Leg Intersection,The data element identifies the leg of the intersection where the pedestrian crash occurred.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB36.,1,Nearside,NA,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDLEG,pedleg,Leg Intersection,The data element identifies the leg of the intersection where the pedestrian crash occurred.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB36.,2,Farside,NA,1,1,1,1,1,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,1a,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,1b,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,1c,"Motorist traveling straight through - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, approach direction unknown",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,2a,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,2b,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,2c,"Motorist traveling straight through - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, approach direction unknown",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,3a,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,3b,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,3c,"Motorist traveling straight through - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, approach direction unknown",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,4a,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,4b,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,4c,"Motorist traveling straight through - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, approach direction unknown",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,5a,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,5b,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,5c,"Motorist turning right - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, approach direction unknown",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,6a,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,6b,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,6c,"Motorist turning right - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, approach direction unknown",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,7a,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,7b,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,7c,"Motorist turning right - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, approach direction unknown",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,8a,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,8b,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,8c,"Motorist turning right - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, approach direction unknown",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,9a,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,9b,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,9c,"Motorist turning left - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, approach direction unknown",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,10a,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,10b,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,10c,"Motorist turning left - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, approach direction unknown",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,11a,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,11b,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,11c,"Motorist turning left - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, approach direction unknown",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,12a,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,12b,NA,NA,1,1,1,1,NA,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,12c,"Motorist turning left - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, approach direction unknown",NA,1,1,1,1,1,NA,NA,NA,NA
FARS,safetyeq,MSAFEQMT,msafeqmt,Non-Motorist Safety Equipment Use,This data element indicates the safety equipment that was used by this non-motorist involved in the crash.,There can be one or more safety equipment responses for each non-motorist.,3,"Reflective Clothing (jacket, backpack, etc.)",NA,1,NA,NA,NA,NA,NA,NA,NA,NA
FARS,safetyeq,MSAFEQMT,msafeqmt,Non-Motorist Safety Equipment Use,This data element indicates the safety equipment that was used by this non-motorist involved in the crash.,There can be one or more safety equipment responses for each non-motorist.,4,"Protective Pads (elbows, knees, shins, etc.)",NA,1,1,NA,NA,NA,NA,NA,NA,NA
FARS,accident,STATENAME,statename,State Name,NA,NA,NA,(Self-evident),NA,NA,1,1,1,1,1,1,1,1
FARS,accident,COUNTYNAME,countyname,County Name,NA,NA,NA,(Self-evident),NA,NA,1,1,1,1,1,1,1,1
FARS,accident,CITYNAME,cityname,City Name,NA,NA,NA,(Self-evident),NA,NA,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",31,"Post, Pole or Other Supports",NA,NA,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",73,Object That Had Fallen From Motor Vehicle In-Transport,NA,NA,1,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",74,Road Vehicle on Rails,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",96,96,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",97,97,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,NUMOCCS,numoccs,Number of Occupants,This data element is a count of the number of occupants in this vehicle.,"All, some, or none of the individuals may have died in the crash. This data element also appears in the Parkwork data file as PNUMOCCS.",98,98,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2404,Jeep / Kaiser-Jeep / Willys- Jeep XYZ_Cherokee (1984-on) (For Grand Cherokee for 2014 on use 02-422.),NA,NA,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6423,Chrysler Pacifica,NA,NA,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20040,Chevrolet Bolt,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30042,Volkswagen Golf/Cabriolet/Cabrio/GTI/ GLI,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30999,Volkswagen Unknown (VOLKSWAGEN),NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32403,Audi Allroad (2013 on.  For 2001-2005 see model 047.),NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34401,"BMW X5 (For 2000-16.  For 2017 on, see model 421).",NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34421,"BMW X5 (For 2017 on. For 2000-16, see model 401)",NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42057,Mercedes-Benz SLC Series,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42422,Mercedes-Benz GLS Class,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45044,Porsche 718,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49056,Toyota 86,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51052,Volvo V90,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51053,Volvo S90,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55043,Hyundai Genesis (G80),NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55044,Hyundai Genesis (G90),NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55045,Hyundai Ioniq,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58047,Infiniti QX30,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62425,Land Rover Discovery,NA,NA,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63403,KIA Niro,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",77707,Victory Electric Motorcycle,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98707,Other Make Electric Motorcycle,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99707,Unknown Make Electric Motorcycle,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",31,"Standard pickup (GVWR 4,500 to 10,00 lbs.)(Jeep Pickup, Comanche, Ram Pickup, D100-D350,....)",NA,NA,1,NA,NA,NA,NA,NA,NA,NA
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",31,"Post, Pole or Other Supports",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",73,Object That Had Fallen From Motor Vehicle In-Transport,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",74,Road Vehicle on Rails,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2016,2016,NA,NA,1,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2016,2016,NA,NA,1,1,1,1,1,1,NA,NA
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,15,Turning Left,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,16,Turning Right,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,17,Crossing over (passing through) Junction,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,20,Backing,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,21,Making a U-Turn,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,64,"From parking Lane/Shoulder, Median/Crossover, Roadside",NA,NA,1,1,1,1,1,NA,NA,NA
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,15,Braking and Unknown Steering Direction,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,16,Braking,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,P_CRASH3,p_crash3,Attempted Avoidance Maneuver,"This data element identifies the attribute that best describes the movements/actions taken by this driver, within a critical crash envelope, in response to the “Critical Precrash Event.”",This data element identifies the actions taken by the driver in response to the impending danger. Because this data element focuses upon the driver’s action just prior to the first harmful event it is coded independently of any maneuvers associated with this vehicle’s “Crash Type.”,99,Unknown/Not Reported,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,0,M0-No Impact,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,1,A1-Single Driver-Right Roadside Departure-Drive Off Road,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,2,A2-Single Driver-Right Roadside Departure-Control/Traction Loss,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,3,"A3-Single Driver-Right Roadside Departure-Avoid Collision With Veh., Ped., Anim.",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,4,A4-Single Driver-Right Roadside Departure-Specifics Other,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,5,A5-Single Driver-Right Roadside Departure-Specifics Unknown,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,6,B6-Single Driver-Left Roadside Departure-Drive Off Road,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,7,B7-Single Driver-Left Roadside Departure-Control/Traction Loss,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,8,"B8-Single Driver-Left Roadside Departure-Avoid Collision With Veh., Ped., Anim.",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,9,B9-Single Driver-Left Roadside Departure-Specifics Other,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,10,B10-Single Driver-Left Roadside Departure-Specifics Unknown,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,11,C11-Single Driver-Forward Impact-Parked Veh.,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,12,C12-Single Driver-Forward Impact-Sta. Object,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,13,C13-Single Driver-Forward Impact-Pedestrian/ Animal,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,14,C14-Single Driver-Forward Impact-End Departure,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,15,C15-Single Driver-Forward Impact-Specifics Other,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,16,C16-Single Driver-Forward Impact-Specifics Unknown,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,20,"D20-Same Trafficway, Same Direction-Rear End-Stopped",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,21,"D21-Same Trafficway, Same Direction-Rear End-Stopped, Straight",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,22,"D22-Same Trafficway, Same Direction-Rear End-Stopped, Left",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,23,"D23-Same Trafficway, Same Direction-Rear End-Stopped, Right",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,24,"D24-Same Trafficway, Same Direction-Rear End-Slower",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,25,"D25-Same Trafficway, Same Direction-Rear End-Slower, Going Straight",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,26,"D26-Same Trafficway, Same Direction-Rear End-Slower, Going Left",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,27,"D27-Same Trafficway, Same Direction-Rear End-Slower, Going Right",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,28,"D28-Same Trafficway, Same Direction-Rear End-Decelerating (Slowing)",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,29,"D29-Same Trafficway, Same Direction-Rear End-Decelerating (Slowing), Going Straight",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,30,"D30-Same Trafficway, Same Direction-Rear End-Decelerating (Slowing), Going Left",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,31,"D31-Same Trafficway, Same Direction-Rear End-Decelerating (Slowing), Going Right",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,32,"D32-Same Trafficway, Same Direction-Rear End-Specifics Other",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,33,"D33-Same Trafficway, Same Direction-Rear End-Specifics Unknown",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,34,"E34-Same Trafficway, Same Direction-Forward Impact-Control/Traction Loss",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,35,"E35-Same Trafficway, Same Direction-Forward Impact-Control/Traction Loss",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,36,"E36-Same Trafficway, Same Direction-Forward Impact-Control/Traction Loss",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,37,"E37-Same Trafficway, Same Direction-Forward Impact-Control/Traction Loss",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,38,"E38-Same Trafficway, Same Direction-Forward Impact-Avoid Collision with Vehicle",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,39,"E39-Same Trafficway, Same Direction-Forward Impact-Avoid Collision with Vehicle",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,40,"E40-Same Trafficway, Same Direction-Forward Impact-Avoid Collision With Object",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,41,"E41-Same Trafficway, Same Direction-Forward Impact-Avoid Collision With Object",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,42,"E42-Same Trafficway, Same Direction-Forward Impact-Specifics Other",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,43,"E43-Same Trafficway, Same Direction-Forward Impact-Specifics Unknown",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,44,"F44-Same Trafficway, Same Direction-Angle, Sideswipe-Straight Ahead on Left",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,45,"F45-Same Trafficway, Same Direction-Angle, Sideswipe-Straight Ahead on Left/Right",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,46,"F46-Same Trafficway, Same Direction-Angle, Sideswipe-Changing Lanes to the Right",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,47,"F47-Same Trafficway, Same Direction-Angle, Sideswipe-Changing Lanes to the Left",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,48,"F48-Same Trafficway, Same Direction-Angle, Sideswipe-Specifics Other",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,49,"F49-Same Trafficway, Same Direction-Angle, Sideswipe-Specifics Unknown",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,50,"G50-Same Trafficway, Opposite Direction-Head-On-Lateral Move (Left/Right)",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,51,"G51-Same Trafficway, Opposite Direction-Head-On-Lateral Move (Going Straight)",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,52,"G52-Same Trafficway, Opposite Direction-Head-On-Specifics Other",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,53,"G53-Same Trafficway, Opposite Direction-Head-On-Specifics Unknown",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,54,"H54-Same Trafficway, Opposite Direction-Forward Impact-Control/Traction Loss",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,55,"H55-Same Trafficway, Opposite Direction-Forward Impact-Control/Traction Loss",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,56,"H56-Same Trafficway, Opposite Direction-Forward Impact-Control/Traction Loss",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,57,"H57-Same Trafficway, Opposite Direction-Forward Impact-Control/Traction Loss",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,58,"H58-Same Trafficway, Opposite Direction-Forward Impact-Avoid Collision With Vehicle",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,59,"H59-Same Trafficway, Opposite Direction-Forward Impact-Avoid Collision With Vehicle",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,60,"H60-Same Trafficway, Opposite Direction-Forward Impact-Avoid Collision With Object",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,61,"H61-Same Trafficway, Opposite Direction-Forward Impact-Avoid Collision With Object",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,62,"H62-Same Trafficway, Opposite Direction-Forward Impact-Specifics Other",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,63,"H63-Same Trafficway, Opposite Direction-Forward Impact-Specifics Unknown",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,64,"I64-Same Trafficway, Opposite Direction-Angle, Sideswipe-Lateral Move (Left/Right)",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,65,"I65-Same Trafficway, Opposite Direction-Angle, Sideswipe-Lateral Move (Going Straight)",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,66,"I66-Same Trafficway, Opposite Direction-Angle, Sideswipe-Specifics Other",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,67,"I67-Same Trafficway, Opposite Direction-Angle, Sideswipe-Specifics Unknown",NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,68,J68-Trafficway Vehicle Turning-Turn Across Path-Initial Opposite Directions (Left/Right),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,69,J69-Trafficway Vehicle Turning-Turn Across Path-Initial Opposite Directions (Going Straight),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,70,J70-Trafficway Vehicle Turning-Turn Across Path-Initial Same Directions (Turning Right),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,71,J71-Trafficway Vehicle Turning-Turn Across Path-Initial Same Directions (Going Straight),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,72,J72-Trafficway Vehicle Turning-Turn Across Path-Initial Same Directions (Turning Left),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,73,J73-Trafficway Vehicle Turning-Turn Across Path-Initial Same Directions (Going Straight),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,74,J74-Trafficway Vehicle Turning-Turn Across Path-Specifics Other,NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,75,J75-Trafficway Vehicle Turning-Turn Across Path-Specifics Unknown,NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,76,K76-Trafficway Vehicle Turning-Turn Into Path-Turn Into Same Direction (Turning Left),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,77,K77-Trafficway Vehicle Turning-Turn Into Path-Turn Into Same Direction (Going Straight),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,78,K78-Trafficway Vehicle Turning-Turn Into Path-Turn Into Same Direction (Turning Right),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,79,K79-Trafficway Vehicle Turning-Turn Into Path-Turn Into Same Direction (Going Straight),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,80,K80-Trafficway Vehicle Turning-Turn Into Path-Turn Into Opposite Directions (Turning Right),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,81,K81-Trafficway Vehicle Turning-Turn Into Path-Turn Into Opposite Directions (Going Straight),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,82,K82-Trafficway Vehicle Turning-Turn Into Path-Turn Into Opposite Directions (Turning Left),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,83,K83-Trafficway Vehicle Turning-Turn Into Path-Turn Into Opposite Directions (Going Straight),NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,84,K84-Trafficway Vehicle Turning-Turn Into Path-Specifics Other,NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,85,K85-Trafficway Vehicle Turning-Turn Into Path-Specifics Unknown,NA,NA,1,1,1,1,1,1,1,NA
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,86,L86-Intersecting Paths-Straight Paths-Striking from the Right,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,87,L87-Intersecting Paths-Straight Paths-Struck on the Right,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,88,L88-Intersecting Paths-Straight Paths-Striking from the Left,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,89,L89-Intersecting Paths-Straight Paths-Struck on the left,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,90,L90-Intersecting Paths-Straight Paths-Specifics Other,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,91,L91-Intersecting Paths-Straight Paths-Specifics Unknown,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,92,M92-Backing-Backing Veh.,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,93,M93-Backing-Other Vehicle,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,98,M98-Other Crash Type,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,99,M99-Unknown,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,TRLR1VIN,trlr1vin,Trailer VIN (1),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",000000000000,No VIN Required,NA,NA,1,1,1,1,1,NA,NA,NA
FARS,vehicle,TRLR1VIN,trlr1vin,Trailer VIN (1),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",888888888888,Not Reported,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,TRLR1VIN,trlr1vin,Trailer VIN (1),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",999999999999,Unknown,NA,NA,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,TRLR1VIN,trlr1vin,Trailer VIN (1),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",777777777777,No Trailing Units,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,TRLR2VIN,trlr2vin,Trailer VIN (2),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",000000000000,No VIN Required,NA,NA,1,1,1,1,1,NA,NA,NA
FARS,vehicle,TRLR2VIN,trlr2vin,Trailer VIN (2),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",888888888888,Not Reported,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,TRLR2VIN,trlr2vin,Trailer VIN (2),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",999999999999,Unknown,NA,NA,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,TRLR2VIN,trlr2vin,Trailer VIN (2),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",777777777777,No Trailing Units,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,TRLR3VIN,trlr3vin,Trailer VIN (3),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",000000000000,No VIN Required,NA,NA,1,1,1,1,1,NA,NA,NA
FARS,vehicle,TRLR3VIN,trlr3vin,Trailer VIN (3),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",888888888888,Not Reported,NA,NA,1,1,1,1,1,1,1,1
FARS,vehicle,TRLR3VIN,trlr3vin,Trailer VIN (3),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",999999999999,Unknown,NA,NA,1,1,1,NA,NA,NA,NA,NA
FARS,vehicle,TRLR3VIN,trlr3vin,Trailer VIN (3),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",777777777777,No Trailing Units,NA,NA,1,1,1,1,1,1,1,1
FARS,person,INJ_SEV,inj_sev,Injury Severity,This data element describes the severity of the injury to this person in the crash using the KABCO scale.,It is important to realize that some States do not always collect data on people who were in a crash but were not injured. If the analysis being performed depends on non-injured occupants— for example some paired comparisons—check the data at the State level. Prior to 2022 the Data Element ID was P8/NM8.,9,Unknown/Not Reported,NA,NA,1,1,1,1,1,1,1,1
FARS,person,DRUG_DET,drug_det,Method of Drug Determination by Police,This data element identifies the method by which the police made the determination as to whether drugs were involved for this person.,Prior to 2019 the Data Element ID was P20/NM19.,2,Drug Recognition Expert (or Evaluator)(DRE) determination,NA,NA,1,1,1,NA,NA,NA,NA,NA
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2017,2017,NA,NA,1,1,1,1,1,1,1,1
FARS,person,DEATH_TM,death_tm,Death Time,This data element records the hour and minute of this person’s death utilizing the 24-hour clock format.,"Four digits; DEATH_HR followed by DEATH_MN, e.g., Valid Military Times 0643 for 6:43 a.m. Prior to 2019 the Data Element ID was P25/NM24. From 2019-2021 the Data Element ID was P25/NM25. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",8888,Not Applicable (Non-fatal),NA,NA,1,1,1,1,1,1,1,1
FARS,person,DEATH_TM,death_tm,Death Time,This data element records the hour and minute of this person’s death utilizing the 24-hour clock format.,"Four digits; DEATH_HR followed by DEATH_MN, e.g., Valid Military Times 0643 for 6:43 a.m. Prior to 2019 the Data Element ID was P25/NM24. From 2019-2021 the Data Element ID was P25/NM25. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",9999,Unknown,NA,NA,1,1,1,1,1,1,1,1
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",93,Non-Motorist Wearing Motorcycle Helmet,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",93,Non-Motorist Wearing Motorcycle Helmet,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",93,Non-Motorist Wearing Motorcycle Helmet,NA,NA,1,1,1,1,NA,NA,NA,NA
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",31,"Post, Pole or Other Supports",NA,NA,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",70,"(Non-harmful, Swaying Trailer/Jackknife)",NA,NA,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",73,Object That Had Fallen From Motor Vehicle In-Transport,NA,NA,1,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",74,Road Vehicle on Rails,NA,NA,1,1,1,1,1,1,1,1
FARS,pbtype,PEDLEG,pedleg,Leg Intersection,The data element identifies the leg of the intersection where the pedestrian crash occurred.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB36.,9,Unknown/None of the Above,NA,NA,1,1,1,1,1,1,1,1
FARS,safetyeq,MSAFEQMT,msafeqmt,Non-Motorist Safety Equipment Use,This data element indicates the safety equipment that was used by this non-motorist involved in the crash.,There can be one or more safety equipment responses for each non-motorist.,3,Reflective Clothing/Carried Item,NA,NA,1,NA,NA,NA,NA,NA,NA,NA
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",91,Unknown Object Not Fixed,NA,NA,NA,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",93,Unknown Fixed Object,NA,NA,NA,1,1,1,1,1,1,1
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,98,Other Registration,NA,NA,NA,1,1,1,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6054,Chrysler Pacifica (Passenger Cars),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6443,Chrysler Pacifica (Light Trucks),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12016,"Ford Crown Victoria  (For 2011 on, code as vehicle model 398)",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12032,"Ford Fiesta  (For 2018 on, code as vehicle model 398)",NA,NA,NA,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12403,Ford EcoSport,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30053,Volkswagen Arteon,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30403,Volkswagen Atlas,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31401,Alfa Romeo Stelvio,NA,NA,NA,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31999,Alfa Romeo Unknown (ALFA ROMEO),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32060,Audi RS3,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34405,BMW X2,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35404,Datsun/Nissan Kicks,NA,NA,NA,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37038,Honda FCX/Clarity,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39032,Jaguar XJ/XJL/XJ6/12/XJR/XJ8/  XJ8L Sedan/Coupe,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39402,Jaguar E-Pace,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39499,Jaguar Unknown (light truck),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49405,Toyota C-HR,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51403,Volvo XC40,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52041,"Mitsubishi iMEV  (For 2018 on, code as vehicle model 398)",NA,NA,NA,1,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52403,Mitsubishi Eclipse Cross,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55039,"Hyundai Azera  (For 2018 on, code as vehicle model 398)",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55041,Hyundai Genesis (For 2017 on. See Models 55-043 and 55-044),NA,NA,NA,1,NA,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55404,Hyundai Kona,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59042,Lexus LC Series,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62401,"Land Rover Discovery (For 2017 on, see model 425)",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62425,"Land Rover Discovery (For model years 1994-2004, see model 401)",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62426,Land Rover Velar,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63041,KIA Stinger,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",34,Light Pickup,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",80,Two Wheel Motorcycle (excluding motor scooters),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",81,Moped or motorized bicycle,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",82,Three-wheel Motorcycle (2 Rear Wheels),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",83,Off-road Motorcycle,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",84,Motor Scooter,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",85,Unenclosed Three Wheel Motorcycle / Unenclosed Autocycle (1 Rear Wheel),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",86,Enclosed Three Wheel Motorcycle / Enclosed Autocycle (1 Rear Wheel),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",87,Unknown Three Wheel Motorcycle Type,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",88,"Other motored cycle type (mini-bikes, pocket motorcycles ""pocket bikes"")",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",96,Recreational Off-Highway Vehicle,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",20,"Object Set in Motion, Unknown if Cargo/Vehicle Parts or Other",NA,NA,NA,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",91,Unknown Object Not Fixed,NA,NA,NA,1,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",93,Unknown Fixed Object,NA,NA,NA,1,1,1,1,1,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2017,2017,NA,NA,NA,1,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2017,2017,NA,NA,NA,1,1,1,1,1,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,55,Improper Management of Vehicle Controls (Specify:),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,56,Object Interference with Vehicle Controls (Specify:),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,57,Driving with Tire-Related Problems,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,60,Alcohol and/or Drug Test Refused,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,55,Improper Management of Vehicle Controls (Specify:),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,56,Object Interference with Vehicle Controls (Specify:),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,57,Driving with Tire-Related Problems,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,60,Alcohol and/or Drug Test Refused,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,55,Improper Management of Vehicle Controls (Specify:),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,56,Object Interference with Vehicle Controls (Specify:),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,57,Driving with Tire-Related Problems,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,60,Alcohol and/or Drug Test Refused,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,55,Improper Management of Vehicle Controls (Specify:),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,56,Object Interference with Vehicle Controls (Specify:),NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,57,Driving with Tire-Related Problems,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,60,Alcohol and/or Drug Test Refused,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,vehicle,VTRAFWAY,vtrafway,Trafficway Description,This data element identifies the attribute that best describes the trafficway flow just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,2,"Two-Way, Divided, Unprotected Median",NA,NA,NA,1,1,1,1,1,1,1
FARS,person,STR_VEH,str_veh,Vehicle Number Of Motor Vehicle Striking Non-Motorist,This data element identifies the “Vehicle Number” (VEH_NO) of the motor vehicle in-transport that made contact with this non-motorist.,"This data element applies only to non-motorists/non-occupants and reflects the vehicle that made contact with the non-motorist/non-occupant identified by the Person Number (PER_NO). The number must match the vehicle number of the striking vehicle. This number is similar to VEH_NO, except that the non-motorist/non-occupant was struck by the vehicle, rather than being within the vehicle. If a non-motorist is hit as a result of a vehicle-to-vehicle collision and it could not be determined which vehicle struck the non-motorist, the lowest vehicle number of the vehicle involved is used. In the element Related Factors – Person Level, the attribute 31 (Default Code Used for Vehicle Numbering) will be coded.",NA,(Self-evident),NA,NA,NA,1,1,1,1,1,1,1
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,8,Person on Personal Conveyances,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,person,INJ_SEV,inj_sev,Injury Severity,This data element describes the severity of the injury to this person in the crash using the KABCO scale.,It is important to realize that some States do not always collect data on people who were in a crash but were not injured. If the analysis being performed depends on non-injured occupants— for example some paired comparisons—check the data at the State level. Prior to 2022 the Data Element ID was P8/NM8.,2,Suspected Minor Injury (B),NA,NA,NA,1,1,1,1,1,1,1
FARS,person,INJ_SEV,inj_sev,Injury Severity,This data element describes the severity of the injury to this person in the crash using the KABCO scale.,It is important to realize that some States do not always collect data on people who were in a crash but were not injured. If the analysis being performed depends on non-injured occupants— for example some paired comparisons—check the data at the State level. Prior to 2022 the Data Element ID was P8/NM8.,3,Suspected Serious Injury (A),NA,NA,NA,1,1,1,1,1,1,1
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",20,None Used / Not Applicable,NA,NA,NA,1,1,NA,NA,NA,NA,NA
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2018,2018,NA,NA,NA,1,1,1,1,1,1,1
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",10,Alcohol and/or Drug Test Refused,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",10,Alcohol and/or Drug Test Refused,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",10,Alcohol and/or Drug Test Refused,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,person,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",3,American Indian (includes Alaska Native),NA,NA,NA,1,1,NA,NA,NA,NA,NA
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",91,Unknown Object Not Fixed,NA,NA,NA,1,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",93,Unknown Fixed Object,NA,NA,NA,1,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,20,"Object Set in Motion, Unknown if Cargo/Vehicle Parts or Other",NA,NA,NA,1,1,1,1,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",4,Paraplegic or in a Wheelchair,NA,NA,NA,1,1,1,1,1,1,1
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,8,Person on Personal Conveyances,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,341,Transit Bus Stop-Related,NA,NA,NA,1,1,1,1,1,1,1
FARS,pbtype,PEDDIR,peddir,Pedestrian Direction,This data element identifies the initial direction of travel of the pedestrian prior to being contacted in the crash.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB33.,9,Not Derived/Unknown Initial Direction of Travel,NA,NA,NA,1,1,1,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,1d,"Motorist traveling straight through - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, other",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,2d,"Motorist traveling straight through - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, other",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,3d,"Motorist traveling straight through - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, other",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,4d,"Motorist traveling straight through - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, other",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,5d,"Motorist turning right - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, other",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,6d,"Motorist turning right - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, other",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,7d,"Motorist turning right - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, other",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,8d,"Motorist turning right - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, other",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,9d,"Motorist turning left - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, other",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,10d,"Motorist turning left - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, other",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,11d,"Motorist turning left - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, other",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,12d,"Motorist turning left - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, other",NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,99,Unknown/Insufficient Information,NA,NA,NA,1,1,1,NA,NA,NA,NA
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,340,Bus Stop-Related,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMHELMET,nmhelmet,Non-Motorist Helmet Use,This data element indicates if the non-motorist was wearing a safety helmet.,"This includes all helmets (e.g., bicycle helmets, motorcycle helmets, racing helmets). Prior to 2019 the Data Element ID was NM13A. From 2019-2021 the Element Data ID was NM14A.",1,No,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMHELMET,nmhelmet,Non-Motorist Helmet Use,This data element indicates if the non-motorist was wearing a safety helmet.,"This includes all helmets (e.g., bicycle helmets, motorcycle helmets, racing helmets). Prior to 2019 the Data Element ID was NM13A. From 2019-2021 the Element Data ID was NM14A.",2,Yes,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMHELMET,nmhelmet,Non-Motorist Helmet Use,This data element indicates if the non-motorist was wearing a safety helmet.,"This includes all helmets (e.g., bicycle helmets, motorcycle helmets, racing helmets). Prior to 2019 the Data Element ID was NM13A. From 2019-2021 the Element Data ID was NM14A.",8,Not Reported,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMHELMET,nmhelmet,Non-Motorist Helmet Use,This data element indicates if the non-motorist was wearing a safety helmet.,"This includes all helmets (e.g., bicycle helmets, motorcycle helmets, racing helmets). Prior to 2019 the Data Element ID was NM13A. From 2019-2021 the Element Data ID was NM14A.",9,Unknown,NA,NA,NA,1,NA,NA,NA,NA,NA,NA
FARS,safetyeq,NMPROPAD,nmpropad,Non-Motorist Use of Protective Pads,"This data element indicates if the non-motorist was wearing padded, shaped attachments to protect specific areas of the body (e.g., elbows, knees, shins) from injury.",Prior to 2019 the Data Element ID was NM13B. From 2019-2021 the Element Data ID was NM14B.,1,No,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMPROPAD,nmpropad,Non-Motorist Use of Protective Pads,"This data element indicates if the non-motorist was wearing padded, shaped attachments to protect specific areas of the body (e.g., elbows, knees, shins) from injury.",Prior to 2019 the Data Element ID was NM13B. From 2019-2021 the Element Data ID was NM14B.,2,Yes,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMPROPAD,nmpropad,Non-Motorist Use of Protective Pads,"This data element indicates if the non-motorist was wearing padded, shaped attachments to protect specific areas of the body (e.g., elbows, knees, shins) from injury.",Prior to 2019 the Data Element ID was NM13B. From 2019-2021 the Element Data ID was NM14B.,8,Not Reported,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMPROPAD,nmpropad,Non-Motorist Use of Protective Pads,"This data element indicates if the non-motorist was wearing padded, shaped attachments to protect specific areas of the body (e.g., elbows, knees, shins) from injury.",Prior to 2019 the Data Element ID was NM13B. From 2019-2021 the Element Data ID was NM14B.,9,Unknown,NA,NA,NA,1,NA,NA,NA,NA,NA,NA
FARS,safetyeq,NMOTHPRO,nmothpro,Non-Motorist Use of Other Protective Safety Equipment,"This data element indicates if the non-motorist was using protective safety equipment other than a helmet or pads (e.g., eye wear/face shields, gloves, wrist guards).",Prior to 2019 the Data Element ID was NM13C. From 2019-2021 the Element Data ID was NM14C.,1,No,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMOTHPRO,nmothpro,Non-Motorist Use of Other Protective Safety Equipment,"This data element indicates if the non-motorist was using protective safety equipment other than a helmet or pads (e.g., eye wear/face shields, gloves, wrist guards).",Prior to 2019 the Data Element ID was NM13C. From 2019-2021 the Element Data ID was NM14C.,2,Yes,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMOTHPRO,nmothpro,Non-Motorist Use of Other Protective Safety Equipment,"This data element indicates if the non-motorist was using protective safety equipment other than a helmet or pads (e.g., eye wear/face shields, gloves, wrist guards).",Prior to 2019 the Data Element ID was NM13C. From 2019-2021 the Element Data ID was NM14C.,8,Not Reported,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMOTHPRO,nmothpro,Non-Motorist Use of Other Protective Safety Equipment,"This data element indicates if the non-motorist was using protective safety equipment other than a helmet or pads (e.g., eye wear/face shields, gloves, wrist guards).",Prior to 2019 the Data Element ID was NM13C. From 2019-2021 the Element Data ID was NM14C.,9,Unknown,NA,NA,NA,1,NA,NA,NA,NA,NA,NA
FARS,safetyeq,NMREFCLO,nmrefclo,Non-Motorist Use of Reflective Clothing/Carried Item,"This data element indicates if the non-motorist was wearing or carrying some type of reflective item (e.g., jacket, backpack, vest).",Prior to 2019 the Data Element ID was NM13D. From 2019-2021 the Element Data ID was NM14D.,1,No,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMREFCLO,nmrefclo,Non-Motorist Use of Reflective Clothing/Carried Item,"This data element indicates if the non-motorist was wearing or carrying some type of reflective item (e.g., jacket, backpack, vest).",Prior to 2019 the Data Element ID was NM13D. From 2019-2021 the Element Data ID was NM14D.,2,Yes,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMREFCLO,nmrefclo,Non-Motorist Use of Reflective Clothing/Carried Item,"This data element indicates if the non-motorist was wearing or carrying some type of reflective item (e.g., jacket, backpack, vest).",Prior to 2019 the Data Element ID was NM13D. From 2019-2021 the Element Data ID was NM14D.,8,Not Reported,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMREFCLO,nmrefclo,Non-Motorist Use of Reflective Clothing/Carried Item,"This data element indicates if the non-motorist was wearing or carrying some type of reflective item (e.g., jacket, backpack, vest).",Prior to 2019 the Data Element ID was NM13D. From 2019-2021 the Element Data ID was NM14D.,9,Unknown,NA,NA,NA,1,NA,NA,NA,NA,NA,NA
FARS,safetyeq,NMLIGHT,nmlight,Non-Motorist Use of Lighting,"This data element indicates if the non-motorist was using a light on his/her person or on a pedalcycle or personal conveyance for safety purposes, to include flashlights.",Prior to 2019 the Data Element ID was NM13E. From 2019-2021 the Element Data ID was NM14E.,1,No,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMLIGHT,nmlight,Non-Motorist Use of Lighting,"This data element indicates if the non-motorist was using a light on his/her person or on a pedalcycle or personal conveyance for safety purposes, to include flashlights.",Prior to 2019 the Data Element ID was NM13E. From 2019-2021 the Element Data ID was NM14E.,2,Yes,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMLIGHT,nmlight,Non-Motorist Use of Lighting,"This data element indicates if the non-motorist was using a light on his/her person or on a pedalcycle or personal conveyance for safety purposes, to include flashlights.",Prior to 2019 the Data Element ID was NM13E. From 2019-2021 the Element Data ID was NM14E.,8,Not Reported,NA,NA,NA,1,1,1,1,1,1,1
FARS,safetyeq,NMLIGHT,nmlight,Non-Motorist Use of Lighting,"This data element indicates if the non-motorist was using a light on his/her person or on a pedalcycle or personal conveyance for safety purposes, to include flashlights.",Prior to 2019 the Data Element ID was NM13E. From 2019-2021 the Element Data ID was NM14E.,9,Unknown,NA,NA,NA,1,NA,NA,NA,NA,NA,NA
FARS,safetyeq,NMOTHPRE,nmothpre,Non-Motorist Use of Other Preventative Safety Equipment,"This data element indicates if the non-motorist was using preventive safety equipment other than a reflective clothing/carried item or light (e.g., bicycle reflectors and flags, reflectors and triangles on a buggy, hi-glo orange clothing, rollerblade stoppers).",Prior to 2019 the Data Element ID was NM13F. From 2019-2021 the Element Data ID was NM14F.,1,No,NA,NA,NA,1,NA,NA,NA,NA,NA,NA
FARS,safetyeq,NMOTHPRE,nmothpre,Non-Motorist Use of Other Preventative Safety Equipment,"This data element indicates if the non-motorist was using preventive safety equipment other than a reflective clothing/carried item or light (e.g., bicycle reflectors and flags, reflectors and triangles on a buggy, hi-glo orange clothing, rollerblade stoppers).",Prior to 2019 the Data Element ID was NM13F. From 2019-2021 the Element Data ID was NM14F.,2,Yes,NA,NA,NA,1,NA,NA,NA,NA,NA,NA
FARS,safetyeq,NMOTHPRE,nmothpre,Non-Motorist Use of Other Preventative Safety Equipment,"This data element indicates if the non-motorist was using preventive safety equipment other than a reflective clothing/carried item or light (e.g., bicycle reflectors and flags, reflectors and triangles on a buggy, hi-glo orange clothing, rollerblade stoppers).",Prior to 2019 the Data Element ID was NM13F. From 2019-2021 the Element Data ID was NM14F.,8,Not Reported,NA,NA,NA,1,NA,NA,NA,NA,NA,NA
FARS,safetyeq,NMOTHPRE,nmothpre,Non-Motorist Use of Other Preventative Safety Equipment,"This data element indicates if the non-motorist was using preventive safety equipment other than a reflective clothing/carried item or light (e.g., bicycle reflectors and flags, reflectors and triangles on a buggy, hi-glo orange clothing, rollerblade stoppers).",Prior to 2019 the Data Element ID was NM13F. From 2019-2021 the Element Data ID was NM14F.,9,Unknown,NA,NA,NA,1,NA,NA,NA,NA,NA,NA
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",4,Paraplegic or in a Wheelchair,NA,NA,NA,1,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",72,"Cargo/Equipment Loss, Shift, or Damage [harmful]",NA,NA,NA,NA,1,1,1,1,1,1
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,accident,MAN_COLL,man_coll,Manner of Collision,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",99,Reported as Unknown,NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,accident,RELJCT1,reljct1,Relation to Junction Within Interchange Area,This data element identifies the crash’s location with respect to presence in an interchange area. The coding of this data element is done in two sub-fields (see also C20B) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20A.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,NA
FARS,accident,RELJCT2,reljct2,Relation to Junction - Specific Location,This data element identifies the crash’s location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20B.,99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,accident,TYP_INT,typ_int,Type of Intersection,This data element identifies and allows separation of various intersection types.,Prior to 2015 the Data Element ID was C21.,99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,12,Pedestrian Refuge Island or Traffic Island,NA,NA,NA,NA,1,1,1,1,1,1
FARS,accident,REL_ROAD,rel_road,Relation To Trafficway,This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event.”,Prior to 2015 the Data Element ID was C22.,99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,accident,LGT_COND,lgt_cond,Light Condition,This data element records the type/level of light that existed at the time of the crash as indicated in the case material.,Prior to 2015 the Data Element ID was C24.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,accident,WEATHER1,weather1,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,accident,WEATHER2,weather2,Atmospheric Conditions,This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,accident,WEATHER,weather,Atmospheric Conditions,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",12,Distracted Driver of a Non-Contact Vehicle,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",24,Unstabilized Situation Began and All Harmful Events Occurred Off of the Roadway,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",12,Distracted Driver of a Non-Contact Vehicle,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",24,Unstabilized Situation Began and All Harmful Events Occurred Off of the Roadway,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",12,Distracted Driver of a Non-Contact Vehicle,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",24,Unstabilized Situation Began and All Harmful Events Occurred Off of the Roadway,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,HIT_RUN,hit_run,Hit and Run,"This data element identifies whether this vehicle was a contact vehicle in the crash that did not stop to render aid (this can include drivers who flee the scene on foot). Hit-and-run is coded when a motor vehicle in-transport or its driver departs from the scene; vehicles not in-transport are excluded. It does not matter whether the hit-and-run vehicle was striking or struck. This data element identifies whether this vehicle was a contact vehicle in the crash that did not stop to render aid (this can include drivers who flee the scene on foot). Hit-and-run is coded when a motor vehicle in-transport, or its driver, departs from the scene; motor vehicles not in- transport are excluded. It does not matter whether the hit-and-run vehicle was striking or struck.","From 1975 to 1981 if no information was known about the Hit-and-Run vehicle and/or driver, the vehicle form and/or driver form were not filled out and were not counted as unknown. Starting in 1982 both a vehicle and a driver form were filled out and the data were identified as unknown. This is why, for example, there were approximately only 20 to 40 drivers with unknown sex listed in the FARS data file from 1975 to 1981 and 700 to 1,000 drivers with unknown sex from 1982 on. In 2009 this data element was no longer collected at the Accident level and is now collected at the Vehicle level. From 1975 to 1981 if no information was known about the Hit-and-Run vehicle and/or driver, the vehicle form and/or driver form were not filled out and were not counted as unknown. Starting in 1982 both a vehicle and a driver form were filled out and the data were identified as unknown. This is why, for example, there were approximately only 20 to 40 drivers with unknown sex listed in the FARS data file from 1975 to 1981 and more than 700 drivers with unknown sex from 1982 on. This data element was removed from Accident data file in 2009. This data element also appears in the Parkwork data file as PHIT_RUN.",9,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,REG_STAT,reg_stat,Vehicle Registration State,This element identifies the State in which this vehicle was registered.,For vehicles with multiple State registrations prior to 1997 the value is 94. In 1997 values 93 and 94 were combined into 93. After 1997 the value for multiple State registrations is 93. This variable also appears in the Parkwork Data File as PREG_STAT.,99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7027,"Dodge Journey (For 2009-2018 only.  For model years 2019 on, see 07-404.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7404,"Dodge Journey (For 2019 on.  For model years 2009-2018, see 07-027.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12024,"Ford Edge (For model years 2007-2018 only.  For model years 2019 on, see 12-424.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12401,"Ford Bronco (thru 1977)/Bronco II/Explorer/Explorer Sport (Explorer for 1990-2018 only.  For model years 2019 on, see 12-425.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12424,"Ford Edge(For 2019 on.  For model years 2007-2018, see 12-024.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12425,Ford Explorer (For 2019 on.  For model years 1990-2018 see 12-401.),NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13403,Lincoln Nautilus,NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13422,Lincoln Nautilus,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19422,Cadillac XT4,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20407,Chevrolet Blazer,NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31401,"Alfa Romeo Stelvio (For 2018 only.  For model years 2019 on, see 31-422.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31422,"Alfa Romeo Stelvio (For 2019 on.  For model year 2018, see 31-401.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32401,"Audi Q7 (For 2007-2018 only.  For model years 2019 on, see 32-422.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32421,Audi Q8,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32422,"Audi Q7 (For 2019 on.  For model years 2007-2018, see 32-401.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34422,BMW X7,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35049,"Datsun/Nissan Murano (For 2003-2018 only.  For model years 2019 on, see 35-422.)",NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35051,"Datsun/Nissan Rogue (For 2008-2018 only.  For model years 2019 on, see 35-404.)",NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35056,Datsun/Nissan Kicks,NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35404,"Datsun/Nissan Rogue (For 2019 on.  For model years 2008-2018, see 35-051.)",NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35422,"Datsun/Nissan Murano (For 2019 on.  For model years 2003-2018, see 35-056.)",NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37422,Honda Passport (2019 on. For 1994-2002 see model 401.),NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38473,Isuzu i-280/i-290,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38474,Isuzu i-350/i-370,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39403,Jaguar I-Pace,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41035,NA,NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42058,Mercedes-Benz A-Class,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42404,"Mercedes-Benz GLE Class (For 2016-2018 only.  For model years 2019 on, see 42-423.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42423,"Mercedes-Benz GLE Class (For 2019 on.  For model years 2016-2018, see 42-404.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42850,Mercedes-Benz Motor Home,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48421,Subaru Ascent,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51050,"Volvo XC60 (For 2008-2018 only.  For model years 2019 on, see 51-404.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51404,"Volvo XC60 (For 2019 on.  For model years 2008-2018, see 51-050.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52047,"Mitsubishi Outlander (For 2003-2018 only.  For model years 2019 on, see 52-404.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52404,"Mitsubishi Outlander (For 2019 on.  For model years 2003-2018, see 52-047.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55041,"Hyundai Genesis (For 2009-2016 only. For model years 2017 on, see 55-043, 55-044 and 55-046)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55046,Hyundai Genesis (G70),NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55405,Hyundai Nexo,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59032,Lexus LS-400/430/460/460L/600h/600hL,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59043,Lexus UX,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63402,KIA Sorento,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",22,"Step-van or walk-in van (GVWR less than or equal to 10,000 lbs.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",55,"Van-Based Bus GVWR greater than 10,000 lbs.",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",60,"Step van (GVWR greater than 10,000 lbs.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",61,"Single-unit straight truck or Cab-Chassis (GVWR range 10,001 to 19,500 lbs.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",62,"Single-unit straight truck or Cab-Chassis (GVWR range 19,501 to 26,000 lbs.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",63,"Single-unit straight truck or Cab-Chassis (GVWR greater than 26,000 lbs.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",67,"Medium/heavy Pickup (GVWR greater than 10,000 lbs.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",71,"Unknown if single-unit or combination unit Medium Truck (GVWR range 10,001 lbs. to 26,000 lbs.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,BODY_TYP,body_typ,Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",72,"Unknown if single-unit or combination unit Heavy Truck (GVWR greater than 26,000 lbs.)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,VIN,vin,Vehicle Identification Number,"This data element records the vehicle identification number (VIN) of this vehicle assigned by the vehicle manufacturer. The VIN contains information on the vehicle such as: manufacturer, model year, model, body type, restraint type, etc.","The vehicle manufacturers use the VIN to describe certain characteristics of a vehicle and to assign a serial number to the vehicle. Starting in 1981 the Vehicle Identification Numbers were required to conform to an international standard. For vehicles built prior to 1981 one may consult the National Automobile Theft Bureau’s publication Passenger Vehicle Identification Manual for the year in question. Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V13. This data element also appears in the Parkwork data file as PVIN.",*,VIN Character Missing or Not Decipherable,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,VIN,vin,Vehicle Identification Number,"This data element records the vehicle identification number (VIN) of this vehicle assigned by the vehicle manufacturer. The VIN contains information on the vehicle such as: manufacturer, model year, model, body type, restraint type, etc.","The vehicle manufacturers use the VIN to describe certain characteristics of a vehicle and to assign a serial number to the vehicle. Starting in 1981 the Vehicle Identification Numbers were required to conform to an international standard. For vehicles built prior to 1981 one may consult the National Automobile Theft Bureau’s publication Passenger Vehicle Identification Manual for the year in question. Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V13. This data element also appears in the Parkwork data file as PVIN.",999999999999,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,MCARR_I1,mcarr_i1,MCID Issuing Authority,This data element records the issuing authority if applicable to this vehicle.,"This data element is only applicable for the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16A. From 2016 to 2019 the Data Element ID was V17A. This data element also appears in the Parkwork data file as PMCARR_I1.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MCARR_I2,mcarr_i2,MCID Identification Number,This data element records the motor carrier identification number if applicable to this vehicle.,"The Carrier Identification Number is found only on vehicles of interstate for-hire or private carriers in the transportation business. It is the unique number assigned to the Carrier by the United States Department of Commerce Commission, or the State. The number can be either a U.S. DOT number (on interstate private carriers) or an ICC MC number (interstate for-hire carriers). Collected only for buses and trucks over 4,500 kg GVWR, this data element is applicable to the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •    Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)         greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16B. From 2016 to 2019 the Data Element ID was V17B. This data element also appears in the Parkwork data file as PMCARR_I2.",999999999,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,MCARR_ID,mcarr_id,Motor Carrier Identification Number,This data element records the issuing authority and motor carrier identification number (if applicable) to this vehicle.,"This 11-character data element is the combination of two data elements, the two-digit “Motor Carrier Issuing Authority” code (MCARR_I1) followed by the nine-character “Identification Number” (MCARR_I2). The Carrier Identification Number is found only on vehicles of interstate for-hire or private carriers in the transportation business. It is the unique number assigned to the Carrier by the United States Department of Commerce Commission or the State. The number can be either a U.S. DOT number (on interstate private carriers) or an ICC MC number (interstate for-hire carriers). Collected only for buses and trucks over 4,500 kg GVWR, this data element is applicable to the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver)    •   Trucks and Vans of any size carrying hazardous cargo.    •   Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)        greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16. From 2016 to 2019 the Data Element ID was V17. This data element also appears in the Parkwork data file as PMCARR_ID.",99999999999,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,GVWR,gvwr,Gross Vehicle Weight Rating,This data element identifies the gross vehicle weight rating of this vehicle if applicable.,"The gross vehicle weight rating (GVWR) or gross combination weight rating (GCWR) is a value specified by the manufacturer for a single-unit truck, truck tractor, or trailer. In the absence of a gross vehicle weight rating, an estimate of the gross weight of a fully loaded unit can be substituted. In 2000 the GVWR was the sum of the weight of the power unit and its trailers. Since 2001 this data element is the gross vehicle weight of the power unit only. The weight of trailers is not added. Prior to 2016 the Data Element ID was V17. Beginning in 2020 this data element is replaced by two data elements, Power Unit GVWR and Trailer GVWR, which are derived from their VINs. This data element also appears in the Parkwork data file as PGVWR.",9,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,CARGO_BT,cargo_bt,Cargo Body Type,This data element describes the primary cargo carrying capability of this vehicle if applicable.,Prior to 2016 the Data Element ID was V19. From 2016 to 2019 the Data Element ID was V20. This data element also appears in the Parkwork data file as PCARGTYP.,99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,BUS_USE,bus_use,Bus Use,This data element describes the common type of bus service this vehicle was being used as at the time of the crash or the primary use for the bus if not in service at the time of the crash.,Prior to 2016 the Data Element ID was V21. From 2016 to 2019 the Data Element ID was V22. This data element also appears in the Parkwork data file as PBUS_USE.,99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,EMER_USE,emer_use,Emergency Use,"This data element identifies whether this vehicle was engaged in emergency use. Emergency Motor Vehicle Use indicates operation of any motor vehicle that is legally authorized by a government authority to respond to emergencies with or without the use of emergency warning equipment, such as a police vehicle, fire truck, or ambulance while actually engaged in such response.",This data element is applicable only if the vehicle was being used as an emergency vehicle at the time of the crash. Prior to 2013 this data element’s name was “Emergency Use.” Prior to 2016 the Data Element ID was V23. From 2016 to 2019 the Data Element ID was V24. This data element also appears in the Person data file and in the Parkwork data file as PEM_USE.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,TRAV_SP,trav_sp,Travel Speed,This data element records the speed the vehicle was traveling prior to the occurrence of the crash as reported by the investigating officer.,"This data is collected after the crash, and is an estimate of the travel speed, which is often a judgment, rather than a measurement. Computing the mean without removing the unknowns will increase the mean travel speed. For the years 1980 and 1981 travel speed was not collected. However, the data element is currently in the database for these 2 years with all data as missing. With this data element there has always been a high number of unknown cases. Since the data were considered somewhat ""uncollectible,"" a decision was made not to collect the data for these 2 years. However, although the data were often unavailable, it was considered too important not to try to collect it. Since 2005 data have been collected for parked motor vehicles and motor vehicles not in- transport. The value 0 only applies to motor vehicles in-transport—for example, a vehicle that is in-transport but stopped at a stop light. Prior to 2016 the Data Element ID was V24. From 2016 to 2019 the Data Element ID was V25.",999,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,DEFORMED,deformed,Extent of Damage,This data element records the amount of damage sustained by this vehicle as indicated in the case material based on an operational damage scale.,The data on 8 (Not Reportable) collected in 1976 are no longer contained in the data file. The data for that year are not consistent with the documentation of the time. The data element name was “Extent of Deformation” from 1975 to 2008. The data element’s name was changed to “Extent of Damage” in 2009. Prior to 2016 the Data Element ID was V29. From 2016 to 2019 the Data Element ID was V30. This data element also appears in the Parkwork Data File as PVEH_SEV.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,TOWED,towed,Vehicle Removal,NA,NA,7,"Towed, Unknown Reason",NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,vehicle,TOWED,towed,Vehicle Removal,NA,NA,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",72,"Cargo/Equipment Loss, Shift, or Damage [harmful]",NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",45,Slide-in Camper,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",45,Slide-in Camper,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,57,Other US Driver`s License,NA,NA,NA,NA,1,1,1,1,1,NA
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,CDL_STAT,cdl_stat,Commercial MV License Status,This data element indicates the status of the driver’s commercial driver’s license (CDL) if applicable.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",7,Commercial Learner`s Permit (CLP),NA,NA,NA,NA,1,1,1,1,1,NA
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,0,None,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,1,1,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,2,2,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,3,3,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,4,4,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,5,5,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,6,6,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,7,7,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,8,8,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,9,9,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,10,10,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,11,11,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,12,12,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,13,13,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,14,14,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,15,15,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,16,16,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,17,17,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,18,18,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,19,19,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,20,20,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,21,21,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,22,22,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,23,23,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,24,24,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,25,25,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,26,26,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,27,27,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,28,28,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,29,29,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,30,30,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,31,31,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,32,32,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,33,33,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,34,34,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,35,35,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,36,36,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,37,37,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,38,38,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,39,39,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,40,40,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,41,41,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,42,42,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,43,43,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,44,44,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,45,45,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,46,46,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,47,47,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,48,48,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,49,49,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,50,50,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,51,51,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,52,52,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,53,53,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,54,54,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,55,55,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,56,56,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,57,57,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,58,58,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,59,59,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,60,60,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,61,61,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,62,62,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,63,63,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,64,64,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,65,65,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,66,66,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,67,67,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,68,68,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,69,69,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,70,70,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,71,71,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,72,72,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,73,73,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,74,74,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,75,75,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,76,76,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,77,77,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,78,78,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,79,79,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,80,80,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,81,81,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,82,82,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,83,83,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,84,84,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,85,85,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,86,86,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,87,87,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,88,88,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,89,89,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,90,90,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,91,91,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,92,92,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,93,93,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,94,94,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,95,95,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,96,96,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,97,97,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,99,Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS1,prev_sus1,Previous Underage Administrative Per Se for BAC,"This data element records any underage pre-conviction administrative license suspension, revocation, or withdrawal in the 5 years prior to the crash date including those for zero-tolerance alcohol violations while driving or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,998,No Driver Present/Unknown if Driver Present,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,0,None,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,1,1,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,2,2,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,3,3,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,4,4,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,5,5,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,6,6,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,7,7,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,8,8,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,9,9,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,10,10,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,11,11,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,12,12,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,13,13,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,14,14,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,15,15,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,16,16,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,17,17,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,18,18,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,19,19,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,20,20,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,21,21,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,22,22,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,23,23,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,24,24,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,25,25,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,26,26,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,27,27,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,28,28,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,29,29,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,30,30,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,31,31,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,32,32,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,33,33,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,34,34,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,35,35,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,36,36,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,37,37,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,38,38,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,39,39,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,40,40,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,41,41,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,42,42,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,43,43,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,44,44,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,45,45,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,46,46,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,47,47,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,48,48,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,49,49,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,50,50,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,51,51,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,52,52,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,53,53,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,54,54,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,55,55,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,56,56,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,57,57,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,58,58,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,59,59,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,60,60,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,61,61,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,62,62,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,63,63,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,64,64,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,65,65,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,66,66,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,67,67,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,68,68,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,69,69,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,70,70,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,71,71,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,72,72,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,73,73,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,74,74,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,75,75,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,76,76,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,77,77,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,78,78,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,79,79,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,80,80,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,81,81,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,82,82,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,83,83,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,84,84,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,85,85,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,86,86,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,87,87,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,88,88,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,89,89,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,90,90,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,91,91,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,92,92,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,93,93,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,94,94,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,95,95,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,96,96,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,97,97,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,99,Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS2,prev_sus2,Previous Administrative Per Se for BAC (Not Underage),"This data element records the count of previous pre-conviction administratively imposed suspensions, revocations, or withdrawals within the 5 years prior to the crash date for driving with a BAC above a specified limit or refusing to submit to chemical testing. This element is only for administrative actions associated with alcohol. These are NOT BAC convictions.",Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.,998,No Driver Present/Unknown if Driver Present,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",0,None,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",1,1,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",2,2,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",3,3,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",4,4,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",5,5,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",6,6,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",7,7,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",8,8,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",9,9,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",10,10,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",11,11,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",12,12,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",13,13,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",14,14,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",15,15,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",16,16,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",17,17,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",18,18,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",19,19,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",20,20,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",21,21,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",22,22,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",23,23,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",24,24,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",25,25,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",26,26,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",27,27,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",28,28,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",29,29,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",30,30,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",31,31,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",32,32,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",33,33,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",34,34,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",35,35,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",36,36,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",37,37,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",38,38,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",39,39,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",40,40,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",41,41,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",42,42,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",43,43,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",44,44,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",45,45,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",46,46,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",47,47,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",48,48,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",49,49,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",50,50,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",51,51,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",52,52,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",53,53,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",54,54,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",55,55,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",56,56,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",57,57,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",58,58,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",59,59,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",60,60,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",61,61,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",62,62,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",63,63,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",64,64,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",65,65,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",66,66,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",67,67,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",68,68,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",69,69,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",70,70,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",71,71,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",72,72,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",73,73,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",74,74,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",75,75,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",76,76,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",77,77,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",78,78,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",79,79,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",80,80,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",81,81,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",82,82,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",83,83,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",84,84,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",85,85,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",86,86,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",87,87,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",88,88,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",89,89,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",90,90,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",91,91,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",92,92,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",93,93,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",94,94,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",95,95,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",96,96,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",97,97,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",99,Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,PREV_SUS3,prev_sus3,"Previous Recorded Other Suspensions, Revocations, or Withdrawals","This data element records any previous license suspensions, revocations, or withdrawals for this driver other than Administrative action for BAC violations within 5 years from the crash date. This element would include administrative actions associated with drugged driving.","Actions resulting from non-traffic related issues or offenses (e.g., failure to pay child support, failure to appear in court for a non-driving offense, a suspension imposed for a drug-related offense not involving the operation of a motor vehicle) are excluded from this count. Also note that “cancellation” of a CDL license is not counted here. A driver who has been disqualified for a CDL is recorded here. Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date.",998,No Driver Present/Unknown if Driver Present,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2018,2018,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2018,2018,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,vehicle,SPEEDREL,speedrel,Speeding Related,"This data element identifies if the driver was speeding, and it was related to the crash as identified by law enforcement.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2013 this data element’s name was “Speed-Related.”",9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,9,Emergency Services Personnel,NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,10,Looked But Did Not See,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,9,Emergency Services Personnel,NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,10,Looked But Did Not See,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,9,Emergency Services Personnel,NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,10,Looked But Did Not See,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,9,Emergency Services Personnel,NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,10,Looked But Did Not See,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vehicle,VTRAFWAY,vtrafway,Trafficway Description,This data element identifies the attribute that best describes the trafficway flow just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,VNUM_LAN,vnum_lan,Total Lanes in Roadway,This data element identifies the attribute that best describes the number of travel lanes just prior to this vehicle’s critical precrash event.,"The number of lanes refers to the number of lanes of a continuous cross-section of roadway. For example, a local roadway with one lane going north and one lane going south would be coded as two lanes. However, if a trafficway is a divided highway with two lanes going north, a median, and two lanes going south, then the number of lanes is coded as two. If a trafficway has two lanes going north immediately adjacent to two lanes going south, one continuous cross-section of roadway, then the number of lanes is coded as four. This data element can be used with the Trafficway Description data element VTRAFWAY to determine the trafficway geometry. For example: If (VNUM_LAN= 2) AND (VTRAFWAY=1), then one has a two-lane roadway that is not physically divided, which is what most people think of as a two-lane road (i.e., one lane going in each direction). If the roadway is a divided trafficway, the number of travel lanes counts only lanes in the direction of travel of the first harmful event. If the roadway is an undivided trafficway, the number of travel lanes are all the lanes regardless of their direction of travel. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.",9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,VSPD_LIM,vspd_lim,Speed Limit,This data element identifies the attribute that best represents the speed limit just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,VALIGN,valign,Roadway Alignment,This data element identifies the attribute that best represents the roadway alignment prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,2,Curve - Right,NA,NA,NA,NA,1,1,1,1,1,NA
FARS,vehicle,VALIGN,valign,Roadway Alignment,This data element identifies the attribute that best represents the roadway alignment prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,3,Curve - Left,NA,NA,NA,NA,1,1,1,1,1,NA
FARS,vehicle,VALIGN,valign,Roadway Alignment,This data element identifies the attribute that best represents the roadway alignment prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,VPROFILE,vprofile,Roadway Grade,This data element identifies the attribute that best represents the roadway grade prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level. Prior to 2010 this data element’s name was Roadway Profile.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,VPAVETYP,vpavetyp,Roadway Surface Type,This data element identifies the attribute that best represents the roadway surface type prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,VSURCOND,vsurcond,Roadway Surface Condition,This data element identifies the attribute that best represents the roadway surface condition prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,VTRAFCON,vtrafcon,Traffic Control Device,This data element identifies the attribute that best describes the traffic controls in the vehicle’s environment just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,VTCONT_F,vtcont_f,Traffic Control Device Functioning,This data element identifies the functionality of the traffic control device recorded for this vehicle in the data element “Traffic Control Device.”,Data not collected prior to 1982. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,TRLR1VIN,trlr1vin,Trailer VIN (1),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",*,VIN Character Missing or Not Decipherable,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,TRLR2VIN,trlr2vin,Trailer VIN (2),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",*,VIN Character Missing or Not Decipherable,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vehicle,TRLR3VIN,trlr3vin,Trailer VIN (3),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",*,VIN Character Missing or Not Decipherable,NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,AGE,age,Age,This data element identifies the person’s age in years on the date of the crash.,NA,999,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,SEX,sex,Sex,This data element identifies the sex of this person involved in the crash.,"From 1975 to 1981, if no information was known about the hit-and-run vehicle and/or driver, then neither the vehicle form nor the driver form was filled out and were not counted in the FARS census. Starting in 1982 both a vehicle and a driver form were filled out and the data were identified as unknown. This is why there were approximately only 20 to 40 drivers with unknown sex listed in the FARS data file from 1975 to 1981 and 700 to 1000 drivers with unknown sex from 1982 on. On March 22, 1995, a quick review of the 1994 Annual Report File revealed that of the 768 people in the 1994 data file with unknown sex; over 90 percent were involved in hit-and-run crashes.",9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,REST_USE,rest_use,Restraint System/Helmet Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",99,Reported as Unknown,NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,person,AIR_BAG,air_bag,Air Bag Deployed,This data element records air bag availability and deployment for this person as reported in the case material.,"This data element is designed to collect both air bag availability and deployment for each occupied seat position. Variation in the presentation of the source data on the State crash report forms and the selections coded on the police crash report may produce unlikely combinations or missing data. For example:    1. If the seat position does not have an air bag at the time of manufacture, but the       information on the police crash report indicates an air bag was available or deployed, the       information on the police crash report may have taken precedence.    2. If the seat position has an air bag installed at the time of manufacture and the police crash       report indicates there is no air bag available, then the police crash report information may       have taken precedence.",99,Reported as Deployment Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,EJECTION,ejection,Ejection,"This data element describes the ejection status and degree of ejection for this person, excluding motorcycle occupants.","In the mid 1970’s there were a large number of people coded as ejection unknown and a corresponding small number of people coded as not ejected. However, the totally ejected and partially ejected counts are the same magnitude as in later years. Starting in 2011 “Not Applicable” includes people not in motor vehicles (pedestrians, bicyclists, etc.)",9,Reported as Unknown if Ejected,NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,DRINKING,drinking,Police Reported Alcohol Involvement,This data element records whether alcohol was involved for this person and reflects the judgment of law enforcement.,"This data element does not indicate that alcohol was a cause of the crash. If a police crash report indicates that opened or unopened alcohol bottles were found in the vehicle, then this information does not by itself constitute involvement. Prior to 2019 the Data Element ID was P16/NM15. From 2019-2021 the Element Data ID was P16/NM16.",9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,ALC_STATUS,alc_status,Alcohol Test- Status,This data element identifies whether an alcohol test was given to this person.,Prior to 2019 the Data Element ID was P18A/NM17A. From 2019-2021 the Data Element ID was P18A/NM18A.,9,Reported as Unknown if Tested,NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,11,"Breath Test, Unknown Type",NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,ATST_TYP,atst_typ,Alcohol Test- Type,This data element identifies the type of alcohol test that was given to this person.,Prior to 2019 the Data Element ID was P18B/NM17B. From 2019-2021 the Data Element ID was P18B/NM18B.,99,Reported as Unknown if Tested,NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,ALC_RES,alc_res,Alcohol Test- Result,This data element identifies the alcohol test result for this person.,In 2015 this data element changed from a two-digit field to a three-digit field. Prior to 2015 the third digit was truncated—not rounded. A BAC of .10 is coded as 10 prior to 2015 and as 100 in 2015 and later. The decimal is implied. The BAC is expressed in grams per deciliter (g/dL) or a clinical evaluation of the same. Prior to 2019 the Data Element ID was P18C/NM17C. From 2019-2021 the Data Element ID was P18C/NM18C.,999,Reported as Unknown if Tested,NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,DRUGS,drugs,Police Reported Drug Involvement,This data element records whether drugs were involved for this person and reflects the judgment of law enforcement.,Prior to 2019 the Data Element ID was P19/NM18. From 2019-2021 the Data Element ID was P19/NM19.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,DSTATUS,dstatus,Drug Test -Status,This data element identifies whether a drug test was given to this person.,Prior to 2019 the Data Element ID was P21A/NM20A. From 2019-2021 the Data Element ID was P21A/NM21A.,9,Reported as Unknown if Tested,NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,HOSPITAL,hospital,Transported to Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",9,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2019,2019,NA,NA,NA,NA,1,1,1,1,1,1
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",31,Default Code Used for Vehicle Numbering,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",31,Default Code Used for Vehicle Numbering,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",31,Default Code Used for Vehicle Numbering,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,99,Reported as Unknown Location,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",72,"Cargo/Equipment Loss, Shift, or Damage [harmful]",NA,NA,NA,NA,1,1,1,1,1,1
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,99,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",99,Reported as Unknown if Distracted,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",99,Reported as Unknown if Impaired,NA,NA,NA,NA,1,1,1,1,1,1
FARS,factor,MFACTOR,mfactor,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,maneuver,MDRMANAV,mdrmanav,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,vision,MVISOBSC,mvisobsc,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,pbtype,PBAGE,pbage,Age,This data element identifies the person’s age in years with respect to the person’s last birthday.,NA,999,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,pbtype,PBSEX,pbsex,Sex,This data element identifies the sex of the person involved in the crash.,NA,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,safetyeq,NMHELMET,nmhelmet,Non-Motorist Helmet Use,This data element indicates if the non-motorist was wearing a safety helmet.,"This includes all helmets (e.g., bicycle helmets, motorcycle helmets, racing helmets). Prior to 2019 the Data Element ID was NM13A. From 2019-2021 the Element Data ID was NM14A.",9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,safetyeq,NMPROPAD,nmpropad,Non-Motorist Use of Protective Pads,"This data element indicates if the non-motorist was wearing padded, shaped attachments to protect specific areas of the body (e.g., elbows, knees, shins) from injury.",Prior to 2019 the Data Element ID was NM13B. From 2019-2021 the Element Data ID was NM14B.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,safetyeq,NMOTHPRO,nmothpro,Non-Motorist Use of Other Protective Safety Equipment,"This data element indicates if the non-motorist was using protective safety equipment other than a helmet or pads (e.g., eye wear/face shields, gloves, wrist guards).",Prior to 2019 the Data Element ID was NM13C. From 2019-2021 the Element Data ID was NM14C.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,safetyeq,NMREFCLO,nmrefclo,Non-Motorist Use of Reflective Clothing/Carried Item,"This data element indicates if the non-motorist was wearing or carrying some type of reflective item (e.g., jacket, backpack, vest).",Prior to 2019 the Data Element ID was NM13D. From 2019-2021 the Element Data ID was NM14D.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,safetyeq,NMLIGHT,nmlight,Non-Motorist Use of Lighting,"This data element indicates if the non-motorist was using a light on his/her person or on a pedalcycle or personal conveyance for safety purposes, to include flashlights.",Prior to 2019 the Data Element ID was NM13E. From 2019-2021 the Element Data ID was NM14E.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,safetyeq,NMOTHPRE,nmothpre,Non-Motorist Use of Other Preventive Safety Equipment,"This data element indicates if the non-motorist was using preventive safety equipment other than a reflective clothing/carried item or light (e.g., bicycle reflectors and flags, reflectors and triangles on a buggy, hi-glo orange clothing, rollerblade stoppers).",Prior to 2019 the Data Element ID was NM13F. From 2019-2021 the Element Data ID was NM14F.,1,No,NA,NA,NA,NA,1,1,1,1,1,1
FARS,safetyeq,NMOTHPRE,nmothpre,Non-Motorist Use of Other Preventive Safety Equipment,"This data element indicates if the non-motorist was using preventive safety equipment other than a reflective clothing/carried item or light (e.g., bicycle reflectors and flags, reflectors and triangles on a buggy, hi-glo orange clothing, rollerblade stoppers).",Prior to 2019 the Data Element ID was NM13F. From 2019-2021 the Element Data ID was NM14F.,2,Yes,NA,NA,NA,NA,1,1,1,1,1,1
FARS,safetyeq,NMOTHPRE,nmothpre,Non-Motorist Use of Other Preventive Safety Equipment,"This data element indicates if the non-motorist was using preventive safety equipment other than a reflective clothing/carried item or light (e.g., bicycle reflectors and flags, reflectors and triangles on a buggy, hi-glo orange clothing, rollerblade stoppers).",Prior to 2019 the Data Element ID was NM13F. From 2019-2021 the Element Data ID was NM14F.,8,Not Reported,NA,NA,NA,NA,1,1,1,1,1,1
FARS,safetyeq,NMOTHPRE,nmothpre,Non-Motorist Use of Other Preventive Safety Equipment,"This data element indicates if the non-motorist was using preventive safety equipment other than a reflective clothing/carried item or light (e.g., bicycle reflectors and flags, reflectors and triangles on a buggy, hi-glo orange clothing, rollerblade stoppers).",Prior to 2019 the Data Element ID was NM13F. From 2019-2021 the Element Data ID was NM14F.,9,Reported as Unknown,NA,NA,NA,NA,1,1,1,1,1,1
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",99,Reported as Unknown if Impaired,NA,NA,NA,NA,1,1,1,1,1,1
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",9,"Stationary and Adjacent to Roadway (e.g., Shoulder, Median, Sidewalk)",NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,nmprior,MPR_ACT,mpr_act,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",99,Reported as Unknown,NA,NA,NA,NA,1,1,NA,NA,NA,NA
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,PER_NO,per_no,Person Number,"This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files.","Each occupant of the vehicle is numbered, and each non-occupant is numbered; in the case of a non-occupant the vehicle number is zero. The numbers for occupants are consecutive for each vehicle beginning with 1. Numbers are never skipped. Drivers do not have to be coded 1. Non- Occupants are identified by vehicle number 0 and are numbered consecutively starting with 1 for each non-motorist. To get drivers see data element PER_TYP under Person Type. PER_NO can be used in merges, e.g., when merging the FARS person data file with the multiple cause of death file.",NA,(Self-evident),NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGSPEC,drugspec,Drug Specimen,This element identifies the bodily tissue or fluid used to perform a chemical test for the presence of drugs in this person.,"Prior to 2018 this data element’s name was ""Drug Test Type"" and identified the type of drug test that was given to this person. The data element was in the Person data file and up to three drug test types could be recorded. See ""Drug Test Type"" under the discontinued data elements of the Person Data file for details. Prior to 2019 the Data Element ID was P21B/NM20B. From 2019-2021 the Data Element ID was P21B/NM21B.",0,Test Not Given,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGSPEC,drugspec,Drug Specimen,This element identifies the bodily tissue or fluid used to perform a chemical test for the presence of drugs in this person.,"Prior to 2018 this data element’s name was ""Drug Test Type"" and identified the type of drug test that was given to this person. The data element was in the Person data file and up to three drug test types could be recorded. See ""Drug Test Type"" under the discontinued data elements of the Person Data file for details. Prior to 2019 the Data Element ID was P21B/NM20B. From 2019-2021 the Data Element ID was P21B/NM21B.",1,Whole Blood,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGSPEC,drugspec,Drug Specimen,This element identifies the bodily tissue or fluid used to perform a chemical test for the presence of drugs in this person.,"Prior to 2018 this data element’s name was ""Drug Test Type"" and identified the type of drug test that was given to this person. The data element was in the Person data file and up to three drug test types could be recorded. See ""Drug Test Type"" under the discontinued data elements of the Person Data file for details. Prior to 2019 the Data Element ID was P21B/NM20B. From 2019-2021 the Data Element ID was P21B/NM21B.",2,Urine,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGSPEC,drugspec,Drug Specimen,This element identifies the bodily tissue or fluid used to perform a chemical test for the presence of drugs in this person.,"Prior to 2018 this data element’s name was ""Drug Test Type"" and identified the type of drug test that was given to this person. The data element was in the Person data file and up to three drug test types could be recorded. See ""Drug Test Type"" under the discontinued data elements of the Person Data file for details. Prior to 2019 the Data Element ID was P21B/NM20B. From 2019-2021 the Data Element ID was P21B/NM21B.",11,Blood Plasma / Serum,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGSPEC,drugspec,Drug Specimen,This element identifies the bodily tissue or fluid used to perform a chemical test for the presence of drugs in this person.,"Prior to 2018 this data element’s name was ""Drug Test Type"" and identified the type of drug test that was given to this person. The data element was in the Person data file and up to three drug test types could be recorded. See ""Drug Test Type"" under the discontinued data elements of the Person Data file for details. Prior to 2019 the Data Element ID was P21B/NM20B. From 2019-2021 the Data Element ID was P21B/NM21B.",12,Blood Clot,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGSPEC,drugspec,Drug Specimen,This element identifies the bodily tissue or fluid used to perform a chemical test for the presence of drugs in this person.,"Prior to 2018 this data element’s name was ""Drug Test Type"" and identified the type of drug test that was given to this person. The data element was in the Person data file and up to three drug test types could be recorded. See ""Drug Test Type"" under the discontinued data elements of the Person Data file for details. Prior to 2019 the Data Element ID was P21B/NM20B. From 2019-2021 the Data Element ID was P21B/NM21B.",13,Oral Fluids,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGSPEC,drugspec,Drug Specimen,This element identifies the bodily tissue or fluid used to perform a chemical test for the presence of drugs in this person.,"Prior to 2018 this data element’s name was ""Drug Test Type"" and identified the type of drug test that was given to this person. The data element was in the Person data file and up to three drug test types could be recorded. See ""Drug Test Type"" under the discontinued data elements of the Person Data file for details. Prior to 2019 the Data Element ID was P21B/NM20B. From 2019-2021 the Data Element ID was P21B/NM21B.",14,Vitreous,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGSPEC,drugspec,Drug Specimen,This element identifies the bodily tissue or fluid used to perform a chemical test for the presence of drugs in this person.,"Prior to 2018 this data element’s name was ""Drug Test Type"" and identified the type of drug test that was given to this person. The data element was in the Person data file and up to three drug test types could be recorded. See ""Drug Test Type"" under the discontinued data elements of the Person Data file for details. Prior to 2019 the Data Element ID was P21B/NM20B. From 2019-2021 the Data Element ID was P21B/NM21B.",15,Liver,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGSPEC,drugspec,Drug Specimen,This element identifies the bodily tissue or fluid used to perform a chemical test for the presence of drugs in this person.,"Prior to 2018 this data element’s name was ""Drug Test Type"" and identified the type of drug test that was given to this person. The data element was in the Person data file and up to three drug test types could be recorded. See ""Drug Test Type"" under the discontinued data elements of the Person Data file for details. Prior to 2019 the Data Element ID was P21B/NM20B. From 2019-2021 the Data Element ID was P21B/NM21B.",96,Not Reported,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGSPEC,drugspec,Drug Specimen,This element identifies the bodily tissue or fluid used to perform a chemical test for the presence of drugs in this person.,"Prior to 2018 this data element’s name was ""Drug Test Type"" and identified the type of drug test that was given to this person. The data element was in the Person data file and up to three drug test types could be recorded. See ""Drug Test Type"" under the discontinued data elements of the Person Data file for details. Prior to 2019 the Data Element ID was P21B/NM20B. From 2019-2021 the Data Element ID was P21B/NM21B.",97,Unknown Specimen,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGSPEC,drugspec,Drug Specimen,This element identifies the bodily tissue or fluid used to perform a chemical test for the presence of drugs in this person.,"Prior to 2018 this data element’s name was ""Drug Test Type"" and identified the type of drug test that was given to this person. The data element was in the Person data file and up to three drug test types could be recorded. See ""Drug Test Type"" under the discontinued data elements of the Person Data file for details. Prior to 2019 the Data Element ID was P21B/NM20B. From 2019-2021 the Data Element ID was P21B/NM21B.",98,Other Specimen,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGSPEC,drugspec,Drug Specimen,This element identifies the bodily tissue or fluid used to perform a chemical test for the presence of drugs in this person.,"Prior to 2018 this data element’s name was ""Drug Test Type"" and identified the type of drug test that was given to this person. The data element was in the Person data file and up to three drug test types could be recorded. See ""Drug Test Type"" under the discontinued data elements of the Person Data file for details. Prior to 2019 the Data Element ID was P21B/NM20B. From 2019-2021 the Data Element ID was P21B/NM21B.",99,Reported as Unknown if Tested,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",0,Test Not Given,NA,NA,NA,NA,1,1,1,1,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1,"Tested, No Drugs Found/Negative",NA,NA,NA,NA,1,1,1,1,1,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",95,Not Reported,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",100,Acetaminophen + Codeine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",101,Acetorphine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",102,Acetyl-alpha-methylfentanyl,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",103,Acetyldihydrocodeine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",104,ACETYLMETHADOL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",105,Alfentanil,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",106,Allylprodine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",107,Alpha-methylfentanyl,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",108,Alphamethythiofentanyl,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",109,Alpha-meprodine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",110,Alphamethadol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",111,ALPHAPRODINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",112,ANILERIDINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",113,APC + CODEINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",114,ASPRIN + CODEINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",115,Benzethidine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",117,Benzylmorphine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",118,Beta-hydroxyfentanyl,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",119,Betacetylmethadol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",120,Beta-meprodine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",121,Betamethadol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",122,Betaprodine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",123,Bezitramide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",124,Buprenorphine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",125,Carfentanil,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",126,Clonitazene,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",127,Codeine methylbromide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",128,CODEINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",129,Cyprenorphine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",130,Desomorphine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",131,Dextromoramide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",133,Diampromide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",134,Diethylthiambutene,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",135,Difenoxin,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",136,DIHYDROCODEINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",137,Dihydromorphine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",138,Dimenoxadol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",139,Dimepheptanol (Racemethadol),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",140,Dimethylthiambutene,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",141,Dioxaphetyl Butyrate,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",142,Diphenoxylate,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",143,Dipipanone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",144,Diprenorphine Hydrochloride,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",146,Ethylmethylthiambutene,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",147,ETHYLMORPHINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",148,Etonitazene,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",149,ETORPHINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",150,Extoxeridine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",151,FENTANYL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",152,FIORINAL + CODEINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",153,Furethidine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",154,Heroin (Diacetylmorphine),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",155,HYDROCODONE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",156,Hydromorphinol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",157,HYDROMORPHONE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",158,Hydroxypethidine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",159,Isomethadone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",160,Ketobemidone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",161,Levomoramide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",162,Levophenacylmorphan,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",163,Levormethorphan,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",164,LEVORPHANOL TARTRATE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",165,MEPERIDINE (Pethidine),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",166,Metazocine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",167,METHADONE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",168,Methyldesorphine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",169,Methyldihydromorphine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",170,Methylfentanyl,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",171,Methylphenylpropionoxypiperidine (MPPP),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",172,Metopon,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",173,Moramide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",174,Morpheridine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",175,Morphine methylsulfonate,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",176,Morphine methylbromide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",177,MORPHINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",178,Myrophine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",179,NALORPHINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",180,Nicocodeine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",181,Nicomorphine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",182,Noracymethadol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",183,Norlevorphanol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",184,Normethadone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",185,Normorphine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",186,Norpipanone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",187,OPIUM,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",188,Oxymorphone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",189,OXYCODONE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",190,Parafluorofentanyl,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",191,PAREGORIC,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",192,PAREPECTOLIN,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",193,PENTAZOCINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",195,Phenadoxone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",196,Phenampromide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",197,Phenanthrine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",198,Phenazocine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",199,Phenomorphan,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",200,Phenoperidine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",202,Pholcodine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",203,Piminodine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",204,Piritramide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",205,Proheptazine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",206,Properidine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",207,Propiram,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",208,"Propoxyphene (Dextropropoxyphene, bulk (non-dosage forms))",NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",209,Racemethorphan,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",210,Racemoramide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",211,Racemorphan,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",212,Sufentanil,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",213,Thebacon,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",214,Thebaine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",215,Thiofentanyl,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",216,Tilidine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",217,Trimeperidine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",218,Butorphanol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",220,Alphacetylmethadol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",221,Beta-Hydroxy-3-methylfentanyl,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",222,Codeine & isoquinoline,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",223,Codeine-N-oxide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",224,Dextropropoxyphene (dosage forms),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",225,Difenenoxin,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",226,Dihydroetrophine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",227,Diprenorphine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",228,Levo-alphacetylmethadol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",229,Levorphanol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",230,Methylthiofentanyl,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",231,Morphine-N-oxide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",232,Opium extract,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",233,Opium fluid extract,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",234,Opium Poppy,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",235,Opium Tincture,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",236,Phenylethyl-phenyl-acetoxypiperidine (PEPAP),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",237,Poppy Straw,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",238,Poppy Straw Concentrate,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",239,Remifentanil,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",240,Codeine combination product 90 mg/du,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",241,Codeine preparations - 200 mg/100 ml or 100 gm,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",242,Difenoxin 1 mg/25ug AtSO4/du,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",243,Difenoxin preparations - 0.5 mg/25 ug AtSO4/du,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",244,Dihydrocodeine combination product 90 mg/du,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",245,Dihydrocodeine preparations 10 mg/100 ml or 100 gm,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",246,Diphenoxylate preparations 2.5 mg/25 ug AtSO4,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",247,Ethylmorphine combination product 15 mg/du,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",248,Ethylmorphine preparations 100 mg/100 ml or 100 gm,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",249,Hydrocodone & isoquinoline alkaloid<15 mg/du,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",250,Hydrocodone combination product<15 mg/du,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",251,Meperidine intermediate-A,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",252,Meperidine intermediate-B,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",253,Meperidine intermediate-C,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",254,Methadone intermediate,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",255,Morphine combination product/50 mg/100 ml or gm,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",256,Opium combination product 25 mg/du,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",257,Opium preparations - 100 mg/100 ml or/100 gm,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",258,"Opium, granulated",NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",259,"Opium, powdered",NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",260,Oripavine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",295,"""Narcotics, Type Unknown""",NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",300,ALPRAZOLAM,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",301,AMOBARBITAL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",302,Barbital,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",303,BARBITURATES,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",304,BENZODIAZEPINES,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",305,Benzylfentanyl,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",306,Bromazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",307,BUTABARBITAL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",308,Butalbital,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",309,Camazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",310,CARBAMATE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",311,Chloral betaine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",312,Chloral Hydrate,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",313,CHLORDIAZEPROXIDE,NA,NA,NA,NA,1,NA,NA,NA,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",314,Chlorhexadol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",315,Clobazam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",316,Clonazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",317,CLORAZEPATE DIPOTASSIUM,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",318,Clotiazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",319,Cloxazolam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",320,Delorazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",321,DIAZEPAM,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",322,Estazolam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",323,ETHCHLORVYNOL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",324,Ethinamate,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",325,Ethyl Ioflazepate,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",326,Fiorinal,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",327,Fludiazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",328,Flunitrazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",330,GLUTETHIMIDE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",331,HALAZEPAM,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",332,Haloxazolam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",333,HEXOBARBITAL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",334,Hydroxyzine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",335,Ketazolam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",336,Loprazolam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",337,LORAZEPAM,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",338,Lormetazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",339,Mebutamate,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",340,Mecloqualone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",341,Medazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",342,MEPHOBARBITAL (Methylphenobarbital),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",343,MEPROBAMATE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",344,METHAQUALONE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",345,METHARBITAL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",346,Methohexital,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",347,METHYPRYLON,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",348,Midazolam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",349,Nimetazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",350,Nitrazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",351,Nordiazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",352,OXAZEPAM,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",353,Oxazolam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",354,Paraldehyde,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",355,PENTOBARBITAL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",356,Petrichloral,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",357,Phencyclohexylamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",358,PHENOBARBITAL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",359,Pinazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",360,PRAZEPAM,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",361,Quazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",362,SECOBARBITAL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",363,Sulfondiethylmethane,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",364,Sulfonethylmethane,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",365,Sulfonmethane,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",366,TALBUTAL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",367,TEMAZEPAM,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",368,Tetrazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",369,Thenylfentanyl,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",370,Thiamylal,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",371,Thiopental (Pentothal),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",372,Tiletamine/Zolazepam (Telazol),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",373,TRAIZOLAM,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",374,TYBAMATE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",376,Carisoprodol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",377,Gamma Hydroxybutryate (GHB),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",378,Amobarbital & non-controlled active ingred.,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",379,Aprobarbital,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",380,Barbituric Acid Derivative,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",383,Dexfenfluramine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",384,Flurazepam,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",385,Sibutramine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",386,Zaleplon,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",387,Zolpidem,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",388,Amobarbital suppository dosage form,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",389,Butobarbital (butethal),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",390,Embutramide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",391,Gamma Hydroxybutyric Acid preparations,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",393,Pentobarbital & noncontrolled active ingred.,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",394,Pentobarbital suppository dosage form,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",395,"""Depressants, Type Unknown""",NA,NA,NA,NA,1,1,1,NA,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",396,Pregabalin,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",397,Secobarbital & noncontrolled active ingred.,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",398,Secobarbital suppository dosage form,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",399,Zopiclone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",400,AMPHETAMINE SULFATE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",401,AMPHETAMINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",402,BENZOYLECGONINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",403,BENZPHETAMINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",404,Cathine (Norpseudoephedrine),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",405,Chlorphentermine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",406,Clortermine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",407,COCAINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",408,DEXTROAMPHETAMINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",409,DIETHYLPROPION,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",410,Ecgonine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",411,Fencamfamin,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",412,FENETHYLLINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",413,Fenfluramine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",414,Fenproporex,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",415,MAZINDOL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",416,Menfenorex,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",417,METHAMPHETAMINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",418,METHYLPHENIDATE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",419,N-Ethylamphetamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",420,PEMOLINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",421,PHENDIMETRAZINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",422,PHENMETRAZINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",423,PHENTERMINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",424,Pipradrol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",425,Propylhexedrine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",426,Pyrovalerone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",427,SPA,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",428,Aminorex,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",429,Cathinone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",430,Coca Leaves,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",431,Dicholoralphenazone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",432,Methcathinone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",433,Modafinil,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",434,Vinbarbital,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",435,Methylone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",436,Lisdexamfetamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",437,Methoxy-Methylenedioxyamphetamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",438,"N, N-Dimethylamphetamine (Dimethylamphetamine)",NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",439,N-Benzylpiperazine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",440,Stimulant compounds previously excepted,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",495,"""Stimulants, Type Unknown""",NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",500,AMPHETAMINE VARIANTS,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",501,BUFOTENINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",503,Diethyltryptamine (DET),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",504,Dimethoxyamphetamine (DMA),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",505,Dimethyltryptamine(DMT),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",507,Dronabinol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",508,N-Ethyl-3-piperidyl benzilate,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",509,IBOGAINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",511,LYSERGIC ACID,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",512,MESCALINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",513,Methylenedioxymethamphetamine (MDMA),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",514,Methoxyamphetamine (PMA),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",515,Methylenedioxyamphetamine (MDA),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",516,Nabilone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",517,PEYOTE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",518,Phenylacetone (P2P),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",519,PSILOCYBIN,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",520,PSILOCYN,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",521,Trimethoxy amphetamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",522,Ketamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",523,Alpha_Ethyltryptamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",524,Bromo-dimethoxyamphetamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",525,Bromo-dimethoxyphenethylamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",527,Lysergic Acid Amide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",528,Lysergic Acid Diethylamide (LSD),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",529,Methylaminorex,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",530,Methyl-dimethoxyamphetamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",531,Methylenedioxy-N-ethylamphetamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",532,Dimethylamphetamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",533,N-Ethyl-1-phenylcyclohexylamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",534,Alpha-methyltryptamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",535,Dimethoxyethylamphetamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",536,Dimethoxy-(n)-propylthiophenethylamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",537,Methoxy-NN-diisopropyltryptamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",538,N-Hydroxymethylenedioxy-amphetamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",539,N-Methylpiperidyl benzilate,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",595,"""Hallucinogens, Type Unknown""",NA,NA,NA,NA,1,1,1,NA,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",600,DELTA 9,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",601,HASHISH OIL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",602,HASHISH,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",603,MARIJUANA/Marihuana,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",604,MARINOL,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",605,Tetrahydrocannabinols (THC),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",695,"""Cannabinoid, Type Unknown""",NA,NA,NA,NA,1,1,1,NA,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",700,Ethylamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",701,Parahexyl (Synhexyl),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",702,PHENCYCLIDINE,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",703,PHENCYCLIDINE ANALOGS,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",704,phenylcyclohexylamine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",705,Piperidinocyclohexane-carbonitrile (PCC),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",706,"""Pyrrolidine (PCPy,PHP,TCPy)""",NA,NA,NA,NA,1,1,1,NA,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",707,Thiophend,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",708,Thienylcyclohexylpiperidine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",709,Phenylcyclohexyl-Pyrrolidine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",710,Thienyl Cyclohexyl Pyrrolidine,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",795,"""PCP, Type Unknown""",NA,NA,NA,NA,1,1,1,NA,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",800,Boldenone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",801,Chlorotestosterone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",803,Dehydrochlomethyltestosterone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",804,Dihydrotesterone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",805,Drostanolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",806,Ethylestrenol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",807,Fluoxymesterone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",808,Formebulone (Formebolone),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",809,Mesterolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",810,Methandienone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",811,Methandranone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",812,Methandriol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",813,Methandrostenolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",814,Methenolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",815,Methyltestosterone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",816,Mibolerone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",817,Nandrolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",818,Norethandrolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",819,Oxandrolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",820,Oxymesterone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",821,Oxymetholone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",822,Stanolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",823,Stanozolol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",824,Testolactone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",825,Testosterone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",826,Trenbolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",827,Clostebol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",828,"Alpha, Beta-dihydroxy-alpha-androstane",NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",829,Alpha-methyl-alpha-beta-dihydroxy-alpha-androstane,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",830,Alpha-methyl-beta-beta-dihydroxy-alpha-androstane,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",831,Alpha-methyl-beta-beta-dihydroxy-androstene,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",832,Alpha-methyl-delta 1-dihydrotestosterone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",833,Alpha-methyl-hydroxynandrolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",834,Androstanedione,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",835,Androstenediol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",836,Androstenedione,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",837,"Beta, beta-dihydroxy-alpha-androstane",NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",838,Bolasterone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",839,Calusterone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",840,Delta 1-dihydrotestosterone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",841,Furazabol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",842,Hydroxy-Nortestosterone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",843,Hydroxytestosterone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",844,Mestanolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",845,Methyldienolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",846,Methyltrienolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",847,Norandrostenediol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",848,Norandrostenedione,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",849,Norbolethone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",850,Norclostebol,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",851,Normethandrolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",852,Stenbolone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",853,Tetrahydrogestrinone,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",895,"Anabolic Steroid, Type Unknown",NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",900,Volatile Solvents (toluene),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",901,Plastic Cement (airplane glue),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",902,Paint and Paint Removers,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",903,"""Petroleum Products (gasoline, kerosene)""",NA,NA,NA,NA,1,1,1,NA,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",904,Lacquer Thinners,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",920,Anesthetic Gases,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",921,Amyl Nitrite,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",923,Butly Nitrite,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",924,Nitrous Oxide,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",925,Ether,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",926,Chloroform,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",940,Aerosols (hydrocarbon),NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",941,Hair spray,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",942,Insecticides,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",943,Glass Chillers,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",944,Frying Pan Lubricants,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",995,"""Inhalants, Type Unknown""",NA,NA,NA,NA,1,1,1,NA,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",996,Other Drug,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",997,"Test For Drug, Results Unknown",NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",998,"Tested For Drugs, Drugs Found, Type unknown/Positive",NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",999,Reported as Unknown if Tested for Drugs,NA,NA,NA,NA,1,1,1,1,NA,NA
FARS,accident,HARM_EV,harm_ev,First Harmful Event,This data element describes the first injury- or-damage producing event of the crash.,"“First Harmful Event” applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the Sequence of Events data element. Starting in 2010 this data element is derived from the “Sequence of Events” data element as the first value that is not between codes 60 and 79 (non-harmful events). See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. Prior to 2015 the Data Element ID was C18. This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PHARM_EV.",98,"Harmful Event, Details Not Reported",NA,NA,NA,NA,NA,1,1,1,1,1
FARS,accident,MAN_COLL,man_coll,Manner of Collision of the First Harmful Event,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",0,The First Harmful Event was Not a Collision with a Motor Vehicle in Transport,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,accident,MAN_COLL,man_coll,Manner of Collision of the First Harmful Event,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",1,Front-to-Rear,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,accident,MAN_COLL,man_coll,Manner of Collision of the First Harmful Event,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",2,Front-to-Front,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,accident,MAN_COLL,man_coll,Manner of Collision of the First Harmful Event,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",6,Angle,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,accident,MAN_COLL,man_coll,Manner of Collision of the First Harmful Event,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",7,Sideswipe - Same Direction,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,accident,MAN_COLL,man_coll,Manner of Collision of the First Harmful Event,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",8,Sideswipe - Opposite Direction,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,accident,MAN_COLL,man_coll,Manner of Collision of the First Harmful Event,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",9,Rear-to-Side,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,accident,MAN_COLL,man_coll,Manner of Collision of the First Harmful Event,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",10,Rear-to-Rear,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,accident,MAN_COLL,man_coll,Manner of Collision of the First Harmful Event,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",11,Other,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,accident,MAN_COLL,man_coll,Manner of Collision of the First Harmful Event,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",98,Not Reported,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,accident,MAN_COLL,man_coll,Manner of Collision of the First Harmful Event,"This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport, it is classified as such.","In the original data files from 1975 to 1977, sideswipe was coded as 5 but has since been changed to 7. These years are not consistent with the documentation of the time. Prior to 2015 the Data Element ID was C19. Prior to 2019 this data element’s name was “Manner of Collision.” This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMAN_COLL.",99,Reported as Unknown,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",26,Prior Non-Recurring Incident,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",28,Regular Congestion,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",30,Obstructed Crosswalks,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,accident,CF1,cf1,Related Factors (1),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",31,Related to a Bus Stop,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",26,Prior Non-Recurring Incident,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",28,Regular Congestion,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",30,Obstructed Crosswalks,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,accident,CF2,cf2,Related Factors (2),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",31,Related to a Bus Stop,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",26,Prior Non-Recurring Incident,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",28,Regular Congestion,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",30,Obstructed Crosswalks,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,accident,CF3,cf3,Related Factors (3),This data element records factors related to the crash expressed in the case material.,"There are also vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4), and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used any of the three data elements to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Note: Starting in 1982 many of the “Related Factors-Crash Level” attributes, values 01-29, are coded as “Related Factors-Driver Level” attributes, values 61-87, in the Vehicle data file. Prior to 2015 the Data Element ID was C31. Beginning in 2020 this data element was no longer collected at the Accident level. It is now collected in the Crashrf data file as CRASHRF.",31,Related to a Bus Stop,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAKE,make,Vehicle Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",35,Nissan/Datsun,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2483,Jeep / Kaiser-Jeep / Willys- Jeep Gladiator,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6444,Chrysler Voyager (2020 on. For 2000-2003 see vehicle make 06-442. For 1984-2000 see Plymouth.),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13403,Lincoln Corsair,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13423,Lincoln Aviator,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19027,Cadillac CT5,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19423,Cadillac XT6,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20407,Chevrolet AMER,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29399,Other Domestic Manufacturers Unknown (automobile),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32406,Audi e-Tron,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34704,BMW 350-449 cc,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34707,BMW Electric Motorcycle,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35031,Nissan/Datsun F-10,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35032,Nissan/Datsun 200SX/240SX,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35033,Nissan/Datsun 210/1200/B210,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35034,"Nissan/Datsun Z-car, ZX",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35035,Nissan/Datsun 310,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35036,Nissan/Datsun 510,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35037,Nissan/Datsun 610,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35038,Nissan/Datsun 710,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35039,Nissan/Datsun 810/Maxima,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35040,Nissan/Datsun Roadster,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35041,Nissan/Datsun 311/411,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35042,Nissan/Datsun Stanza,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35043,Nissan/Datsun Sentra,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35044,Nissan/Datsun Pulsar,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35045,Nissan/Datsun Micra,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35046,Nissan/Datsun NX 1600/2000,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35047,Nissan/Datsun Altima,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35048,Nissan/Datsun 350Z/370Z,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35049,"Nissan/Datsun Murano (For 2003-2018 only.  For model years 2019 on, see 35-422.)",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35050,Nissan/Datsun Versa,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35051,"Nissan/Datsun Rogue (For 2008-2018 only.  For model years 2019 on, see 35-404.)",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35052,Nissan/Datsun Cube,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35053,Nissan/Datsun GT-R,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35055,Nissan/Datsun Leaf,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35056,Nissan/Datsun Kicks,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35398,Nissan/Datsun Other (automobile),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35399,Nissan/Datsun Unknown (automobile),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35401,Nissan/Datsun Pathfinder,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35402,Nissan/Datsun Xterra,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35403,Nissan/Datsun Juke,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35404,"Nissan/Datsun Rogue (For 2019 on.  For model years 2008-2018, see 35-051.)",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35421,Nissan/Datsun Pathfinder Armada,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35422,"Nissan/Datsun Murano (For 2019 on.  For model years 2003-2018, see 35-056.)",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35441,Nissan/Datsun Van,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35442,Nissan/Datsun Axxess,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35443,Nissan/Datsun Quest,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35444,Nissan/Datsun Altra EV*,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35446,Nissan/Datsun NV200/eNV200,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35461,Nissan/Datsun NV,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35471,Nissan/Datsun Nissan/Datsun Pickup (1955-1997),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35472,Nissan/Datsun Frontier (1998 on),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35473,Nissan/Datsun Titan (from 2004-06; see 481 for 2007 on),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35481,Nissan/Datsun Titan (from 2007 on; see 473 for 2004-06),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35498,Nissan/Datsun Other (light truck),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35499,Nissan/Datsun Unknown (light truck),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35870,Nissan/Datsun Medium/Heavy Van-Based Vehicle,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35883,Nissan/Datsun Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35898,Nissan/Datsun Other (medium/heavy truck),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35999,Nissan/Datsun Unknown (NISSAN/DATSUN),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37032,"Honda Accord (Note: For Crosstour model years 2010 and 2011 only. For Crosstour model years 2012-2015, see vehicle model 37-405)",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37405,Honda Crosstour (2012-2015 only. See vehicle model 37-032 for model years 2010 and 2011.),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41035,Mazda 323/GLC/ Protege/ Protege5,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42406,Mercedes-Benz GLB Class,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45045,Porsche Taycan,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49057,Toyota GR Supra,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52041,"Mitsubishi iMiEV  (For 2018 on, code as vehicle model 398)",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55406,Hyundai Venue,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55422,Hyundai Palisade,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55498,Hyundai Other (light truck),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62427,Land Rover Defender,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63422,KIA Telluride,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69062,Other Import Caterham,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69398,Other Import Other (automobile),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69399,Other Import Unknown (automobile),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72707,Harley-Davidson Electric Motorcycle,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,10,Safety Service Patrols - Incident Response,NA,NA,NA,NA,NA,1,NA,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,11,Other Incident Response,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,12,Towing - Incident Response,NA,NA,NA,NA,NA,1,NA,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,20,Vehicle Used for Electronic Ride-hailing (Transportation Network Company),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,21,Mail Carrier,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,22,Public Utility,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,23,"Rental Truck over 10,000 lbs.",NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,24,Truck Operating with Crash Attenuator Equipment,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vehicle,IMPACT1,impact1,Areas of Impact - Initial Contact Point,"This data element identifies the area on this vehicle that produced the first instance of injury to non-motorists or occupants of this vehicle, or that resulted in the first instance of damage to other property or to this vehicle.","Prior to 2010 this data element’s name was “Initial Point of Impact.” In 2010 and 2011 its name was “Initial Damaged Area.” Since 2012 its name is “Initial Contact Point.” Prior to 2016 the Data Element ID was V28A. From 2016 to 2019 the Data Element ID was V29A. Starting in 2010 this data element is derived from the crash events for the vehicle. It is the first recorded “Areas of Impact (This Vehicle)” value for this vehicle. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. The attributes Underride and Override were discontinued in 1993 and “Underride/Override” became its own data element in 1994 and then changed again in 2021. Prior to 1994 the striking vehicle, not the vehicle struck, determined the underride/override condition. After the crash, in the case of an override or underride one vehicle is over the other. If the striking vehicle is over the other, then the crash is an override. If the striking vehicle is under the other, the crash is an underride. See the information under “Underride/Override” about using this data element. To understand how the coding of underride and override changed in 2021, see new Vehicle Underride/Override Data Element. This data element also appears in the Person data file and in the Parkwork data file as PIMPACT1.",19,Other Objects or Person Set-In-Motion,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vehicle,M_HARM,m_harm,Most Harmful Event,"This data element describes the event that resulted in the most severe injury or, if no injury, the greatest property damage involving this vehicle.","“First Harmful Event” (HARM_EV) applies to the crash. “Most Harmful Event” (M_HARM) applies to the vehicle. Harmful events are judgment calls of the FARS analysts based on the data within the police crash report. From 2004 to 2009 the data elements “First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” have the same attributes. The harmful event attributes were modified to be consistent with the sequence of events data elements. Starting in 2009 these data elements still have the same attributes except non-harmful event attributes were added to the “Sequence of Events” data element. Prior to 2016 the Data Element ID was V32. From 2016 to 2019 the Data Element ID was V33. This data element also appears in the Parkwork data file as PM_HARM.",98,"Harmful Event, Details Not Reported",NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vehicle,VEH_SC1,veh_sc1,Vehicle Related Factors (1),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",29,Default Code Used for Vehicle Numbering,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,VEH_SC2,veh_sc2,Vehicle Related Factors (2),This data element records factors related to this vehicle expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), driver level related factors in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4) and person level related factors in the Person data file (P_SF1, P_SF2, and P_SF3). The FARS analyst may have used either of the two data elements to code a related factor. One must test both data elements to ensure that the selected related factor is included. The set of Pre-Existing Vehicle Defects that had been collected under “Related Factors—Vehicle Level” is now captured in the precrash level data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). These data elements also appear in the Parkwork data file as PVEH_CF1 and PVEH_CF2 in 2009 and prior and as PVEH_SC1 and PVEH_SC2 in 2010 and later. Prior to 2016 the Data Element ID was V33. From 2017 to 2018 the Data Element ID was V34. Beginning in 2020 this data element was no longer collected at the Vehicle level. It is now collected in the Vehiclesf data file as VEHICLESF.",29,Default Code Used for Vehicle Numbering,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2019,2019,NA,NA,NA,NA,NA,1,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2019,2019,NA,NA,NA,NA,NA,1,1,1,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,29,Intentional Illegal Driving Off the Roadway,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,94,Emergency Medical Service Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,95,Fire Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,96,Tow Operator,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF1,dr_sf1,Driver Related Factors (4 choices),NA,NA,97,"Transportation (i.e. maintenance workers, safety service patrol operators, etc.)",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,29,Intentional Illegal Driving Off the Roadway,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,94,Emergency Medical Service Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,95,Fire Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,96,Tow Operator,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF2,dr_sf2,Driver Related Factors (4 choices),NA,NA,97,"Transportation (i.e. maintenance workers, safety service patrol operators, etc.)",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,29,Intentional Illegal Driving Off the Roadway,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,94,Emergency Medical Service Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,95,Fire Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,96,Tow Operator,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF3,dr_sf3,Driver Related Factors (4 choices),NA,NA,97,"Transportation (i.e. maintenance workers, safety service patrol operators, etc.)",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,29,Intentional Illegal Driving Off the Roadway,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,94,Emergency Medical Service Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,95,Fire Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,96,Tow Operator,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,DR_SF4,dr_sf4,Driver Related Factors (4 choices),NA,NA,97,"Transportation (i.e. maintenance workers, safety service patrol operators, etc.)",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,vehicle,VTCONT_F,vtcont_f,Traffic Control Device Functioning,This data element identifies the functionality of the traffic control device recorded for this vehicle in the data element “Traffic Control Device.”,Data not collected prior to 1982. In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,4,"Device Not Functioning or Device Functioning Improperly, Specifics Unknown",NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,5,"Suddenly Encountered Poor Road Conditions [Puddle, Pot Hole, Ice, Etc.][Specify:]",NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,6,Traveling Too Fast for Conditions or Road Configuration,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,59,Unknown Travel Direction/Speed of Other Motor Vehicle in Lane,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vehicle,TRLR1VIN,trlr1vin,Trailer VIN (1),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",999999999999,Reported as Unknown,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vehicle,TRLR2VIN,trlr2vin,Trailer VIN (2),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",999999999999,Reported as Unknown,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vehicle,TRLR3VIN,trlr3vin,Trailer VIN (3),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",999999999999,Reported as Unknown,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,SEAT_POS,seat_pos,Seating Position,This data element identifies the location of this person in or on the vehicle.,NA,56,Appended to a Motor Vehicle for Motion,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",1,Shoulder Belt Only Used,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",2,Lap Belt Only Used,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",3,Shoulder and Lap Belt Used,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",4,Child Restraint Type Unknown,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",6,Racing-Style Harness Used,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",8,Restraint Used - Type Unknown,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",10,Child Restraint System - Forward Facing,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",11,Child Restraint System - Rear Facing,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",12,Booster Seat,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",20,None Used/Not Applicable,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",96,Not a Motor Vehicle Occupant,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",97,Other,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",98,Not Reported,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_USE,rest_use,Type of Restraint System in Use,This data element records the restraint equipment in use by this occupant at the time of the crash.,"Prior to 2019 this data element’s name was “Restraint System/Helmet Use” that included helmet use, and the Data Element ID was P10. Starting in 2019 helmet use is captured as part of the data element “Helmet Use.”",99,Reported as Unknown,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,REST_MIS,rest_mis,Restraint - Any Indication of Mis-Use,This data element identifies any misuse of the available restraint system used by this person.,"Prior to 2019 this data element’s name was “Indication of Misuse of Restraint System/Helmet” that included helmet misuse, and the Data Element ID was P11. Starting in 2019 helmet misuse is captured as part of the data element “Indication of Helmet Misuse.”",0,No Indication of Mis-Use,NA,NA,NA,NA,NA,1,1,NA,NA,NA
FARS,person,REST_MIS,rest_mis,Restraint - Any Indication of Mis-Use,This data element identifies any misuse of the available restraint system used by this person.,"Prior to 2019 this data element’s name was “Indication of Misuse of Restraint System/Helmet” that included helmet misuse, and the Data Element ID was P11. Starting in 2019 helmet misuse is captured as part of the data element “Indication of Helmet Misuse.”",1,"Yes, Indication of Mis-Use",NA,NA,NA,NA,NA,1,1,NA,NA,NA
FARS,person,REST_MIS,rest_mis,Restraint - Any Indication of Mis-Use,This data element identifies any misuse of the available restraint system used by this person.,"Prior to 2019 this data element’s name was “Indication of Misuse of Restraint System/Helmet” that included helmet misuse, and the Data Element ID was P11. Starting in 2019 helmet misuse is captured as part of the data element “Indication of Helmet Misuse.”",7,None Used/Not Applicable,NA,NA,NA,NA,NA,1,1,NA,NA,NA
FARS,person,REST_MIS,rest_mis,Restraint - Any Indication of Mis-Use,This data element identifies any misuse of the available restraint system used by this person.,"Prior to 2019 this data element’s name was “Indication of Misuse of Restraint System/Helmet” that included helmet misuse, and the Data Element ID was P11. Starting in 2019 helmet misuse is captured as part of the data element “Indication of Helmet Misuse.”",8,Not a Motor Vehicle Occupant,NA,NA,NA,NA,NA,1,1,NA,NA,NA
FARS,person,ALC_DET,alc_det,Method of Alcohol Determination by Police,NA,NA,3,Standard Field Sobriety Test,NA,NA,NA,NA,NA,1,1,1,NA,NA
FARS,person,DRUG_DET,drug_det,Method of Drug Determination by Police,This data element identifies the method by which the police made the determination as to whether drugs were involved for this person.,Prior to 2019 the Data Element ID was P20/NM19.,2,Drug Recognition Expert (or Evaluator) (DRE),NA,NA,NA,NA,NA,1,1,1,NA,NA
FARS,person,DRUG_DET,drug_det,Method of Drug Determination by Police,This data element identifies the method by which the police made the determination as to whether drugs were involved for this person.,Prior to 2019 the Data Element ID was P20/NM19.,3,Observed Behavior or SFST,NA,NA,NA,NA,NA,1,1,1,NA,NA
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2020,2020,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",53,Non-Motorist Previously Used a Motor Vehicle for Motion,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",54,Non-Motorist Attempting to Use a Motor Vehicle for Motion,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",55,"Non-Motorist Attempting to Use or Previously Used a Motor Vehicle for Motion, Details Not Reported",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",94,Emergency Medical Service Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",95,Fire Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",96,Tow Operator,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF1,p_sf1,Related Factors (1),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",97,"Transportation (i.e. maintenance workers, safety service patrol operators, etc.)",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",53,Non-Motorist Previously Used a Motor Vehicle for Motion,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",54,Non-Motorist Attempting to Use a Motor Vehicle for Motion,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",55,"Non-Motorist Attempting to Use or Previously Used a Motor Vehicle for Motion, Details Not Reported",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",94,Emergency Medical Service Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",95,Fire Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",96,Tow Operator,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF2,p_sf2,Related Factors (2),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",97,"Transportation (i.e. maintenance workers, safety service patrol operators, etc.)",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",53,Non-Motorist Previously Used a Motor Vehicle for Motion,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",54,Non-Motorist Attempting to Use a Motor Vehicle for Motion,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",55,"Non-Motorist Attempting to Use or Previously Used a Motor Vehicle for Motion, Details Not Reported",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",94,Emergency Medical Service Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",95,Fire Personnel,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",96,Tow Operator,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,P_SF3,p_sf3,Related Factors (3),This data element records factors related to motor vehicle occupants other than drivers and people not in motor vehicles as expressed in the case material.,"There are also crash level related factors in the Accident data file (CF1, CF2, and CF3), vehicle level related factors in the Vehicle data file (VEH_SC1 and VEH_SC2), and driver level related factors, also in the Vehicle data file (DR_SF1, DR_SF2, DR_SF3, and DR_SF4). Any of the three data elements may have been used to code a related factor. One must test all three data elements to ensure that the selected related factor is included. Person-related factors for all drivers are coded 00. Person-related factors for non-drivers can have non-zero values as listed below.",97,"Transportation (i.e. maintenance workers, safety service patrol operators, etc.)",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,person,HELM_USE,helm_use,Helmet Use,This data element records the helmet use by this occupant at the time of the crash.,"This data element is applicable to occupants of body types 80-91, 96, and 97. (See Body Type.) Prior to 2019 this data was collected as part of the data element “Restraint System/Helmet Use,” and the Data Element ID was P10. Bicycle helmets are sometimes worn while riding a variety of personal conveyances.",5,DOT-Compliant Motorcycle Helmet,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,HELM_USE,helm_use,Helmet Use,This data element records the helmet use by this occupant at the time of the crash.,"This data element is applicable to occupants of body types 80-91, 96, and 97. (See Body Type.) Prior to 2019 this data was collected as part of the data element “Restraint System/Helmet Use,” and the Data Element ID was P10. Bicycle helmets are sometimes worn while riding a variety of personal conveyances.",16,"Helmet, Other than DOT-Compliant Motorcycle Helmet",NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,HELM_USE,helm_use,Helmet Use,This data element records the helmet use by this occupant at the time of the crash.,"This data element is applicable to occupants of body types 80-91, 96, and 97. (See Body Type.) Prior to 2019 this data was collected as part of the data element “Restraint System/Helmet Use,” and the Data Element ID was P10. Bicycle helmets are sometimes worn while riding a variety of personal conveyances.",17,No Helmet,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,HELM_USE,helm_use,Helmet Use,This data element records the helmet use by this occupant at the time of the crash.,"This data element is applicable to occupants of body types 80-91, 96, and 97. (See Body Type.) Prior to 2019 this data was collected as part of the data element “Restraint System/Helmet Use,” and the Data Element ID was P10. Bicycle helmets are sometimes worn while riding a variety of personal conveyances.",19,"Helmet, Unknown if DOT-Compliant",NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,HELM_USE,helm_use,Helmet Use,This data element records the helmet use by this occupant at the time of the crash.,"This data element is applicable to occupants of body types 80-91, 96, and 97. (See Body Type.) Prior to 2019 this data was collected as part of the data element “Restraint System/Helmet Use,” and the Data Element ID was P10. Bicycle helmets are sometimes worn while riding a variety of personal conveyances.",20,Not Applicable,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,HELM_USE,helm_use,Helmet Use,This data element records the helmet use by this occupant at the time of the crash.,"This data element is applicable to occupants of body types 80-91, 96, and 97. (See Body Type.) Prior to 2019 this data was collected as part of the data element “Restraint System/Helmet Use,” and the Data Element ID was P10. Bicycle helmets are sometimes worn while riding a variety of personal conveyances.",96,Not a Motor Vehicle Occupant,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,HELM_USE,helm_use,Helmet Use,This data element records the helmet use by this occupant at the time of the crash.,"This data element is applicable to occupants of body types 80-91, 96, and 97. (See Body Type.) Prior to 2019 this data was collected as part of the data element “Restraint System/Helmet Use,” and the Data Element ID was P10. Bicycle helmets are sometimes worn while riding a variety of personal conveyances.",98,Not Reported,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,HELM_USE,helm_use,Helmet Use,This data element records the helmet use by this occupant at the time of the crash.,"This data element is applicable to occupants of body types 80-91, 96, and 97. (See Body Type.) Prior to 2019 this data was collected as part of the data element “Restraint System/Helmet Use,” and the Data Element ID was P10. Bicycle helmets are sometimes worn while riding a variety of personal conveyances.",99,Reported as Unknown if Helmet Worn,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,person,HELM_MIS,helm_mis,Helmet - Any Indication of Mis-Use,This data element identifies any misuse of the helmet used by this person.,"This data element is applicable to occupants of body types 80-91, 96, and 97. Prior to 2019 this data was collected as part of the data element “Indication of Misuse of Restraint System/Helmet,” and the Data Element ID was P11.",0,No Indication of Mis-Use,NA,NA,NA,NA,NA,1,1,NA,NA,NA
FARS,person,HELM_MIS,helm_mis,Helmet - Any Indication of Mis-Use,This data element identifies any misuse of the helmet used by this person.,"This data element is applicable to occupants of body types 80-91, 96, and 97. Prior to 2019 this data was collected as part of the data element “Indication of Misuse of Restraint System/Helmet,” and the Data Element ID was P11.",1,"Yes, Indication of Mis-Use",NA,NA,NA,NA,NA,1,1,NA,NA,NA
FARS,person,HELM_MIS,helm_mis,Helmet - Any Indication of Mis-Use,This data element identifies any misuse of the helmet used by this person.,"This data element is applicable to occupants of body types 80-91, 96, and 97. Prior to 2019 this data was collected as part of the data element “Indication of Misuse of Restraint System/Helmet,” and the Data Element ID was P11.",7,None Used/Not Applicable,NA,NA,NA,NA,NA,1,1,NA,NA,NA
FARS,person,HELM_MIS,helm_mis,Helmet - Any Indication of Mis-Use,This data element identifies any misuse of the helmet used by this person.,"This data element is applicable to occupants of body types 80-91, 96, and 97. Prior to 2019 this data was collected as part of the data element “Indication of Misuse of Restraint System/Helmet,” and the Data Element ID was P11.",8,Not a Motor Vehicle Occupant,NA,NA,NA,NA,NA,1,1,NA,NA,NA
FARS,vsoe,SOE,soe,Sequence of Events,This data element describes this event. A motor vehicle traffic crash is a series of events resulting from an unstabilized situation. This series of harmful and non-harmful events is recorded in chronological order based on the police crash report narrative and diagram.,"“First Harmful Event,” “Most Harmful Event,” and the “Sequence of Events” data elements have the same harmful event attributes. The harmful event attributes were modified to be consistent. “Sequence of Events” also has non-harmful event attributes. From 2004 to 2009 Sequence of Events was collected at the vehicle level and up to six events (SEQ1-SEQ6) were stored in the Vehicle data file. Prior to 2016 the Data Element ID was V31. From 2016 to 2019 the Data Element ID was V32.",98,"Harmful Event, Details Not Reported",NA,NA,NA,NA,NA,1,1,1,1,1
FARS,vsoe,AOI,aoi,Areas of Impact,"This data element identifies the impact point, if any, on this motor vehicle in-transport that produced property damage or personal injury in this event.",This is the impact area of the vehicle recorded as “Vehicle Number (This Vehicle)” or “Vehicle Number (Other Vehicle)” in the crash events. Prior to 2015 the Data Element ID was C17.,19,Other Objects or Person Set-In-Motion,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",5,While Talking or Listening to Mobile Phone,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",6,While Manipulating Mobile Phone,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",15,Other Mobile Phone Related,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,distract,MDRDSTRD,mdrdstrd,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",98,Other Distraction [Specify:],NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,140,Vehicle into Vehicle or Vehicle into Object,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,1a,"Motorist traveling straight through - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, traveled from motorist`s left",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,1b,"Motorist traveling straight through - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, traveled from motorist`s right",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,2a,"Motorist traveling straight through - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, traveled from motorist`s left",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,2b,"Motorist traveling straight through - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, traveled from motorist`s right",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,3a,"Motorist traveling straight through - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, traveled from motorist`s left",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,3b,"Motorist traveling straight through - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, traveled from motorist`s right",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,4a,"Motorist traveling straight through - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, traveled from motorist`s left",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,4b,"Motorist traveling straight through - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, traveled from motorist`s right",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,5a,"Motorist turning right - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, traveled from motorist`s left",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,5b,"Motorist turning right - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, traveled from motorist`s right",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,6a,"Motorist turning right - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, traveled from motorist`s left",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,6b,"Motorist turning right - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, traveled from motorist`s right",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,7a,"Motorist turning right - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, approach direction same as motorist`s",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,7b,"Motorist turning right - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, approach direction opposite motorist`s",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,8a,"Motorist turning right - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, approach direction same as motorist`s",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,8b,"Motorist turning right - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, approach direction opposite motorist`s",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,9a,"Motorist turning left - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, traveled from motorist`s left",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,9b,"Motorist turning left - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, traveled from motorist`s right",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,10a,"Motorist turning left - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, traveled from motorist`s left",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,10b,"Motorist turning left - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, traveled from motorist`s right",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,11a,"Motorist turning left - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, approach direction same as motorist`s",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,11b,"Motorist turning left - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, approach direction opposite motorist`s",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,12a,"Motorist turning left - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, approach direction same as motorist`s",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,12b,"Motorist turning left - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, approach direction opposite motorist`s",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",1,Dart-Out - Visual Obstruction Noted,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmcrash,MTM_CRSH,mtm_crsh,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",11,"Dash - Run, No Visual Obstruction Noted",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,PER_NO,per_no,Person Number,"This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files.","Each occupant of the vehicle is numbered, and each non-occupant is numbered; in the case of a non-occupant the vehicle number is zero. The numbers for occupants are consecutive for each vehicle beginning with 1. Numbers are never skipped. Drivers do not have to be coded 1. Non- Occupants are identified by vehicle number 0 and are numbered consecutively starting with 1 for each non-motorist. To get drivers see data element PER_TYP under Person Type. PER_NO can be used in merges, e.g., when merging the FARS person data file with the multiple cause of death file.",NA,(Self-evident),NA,NA,NA,NA,NA,1,1,1,1,1
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",0,Not Distracted,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",2,By Other Non-Motorist(s),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",3,By a Driver or Occupant of a Motor Vehicle,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",5,While Talking or Listening to Mobile Phone,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",6,While Manipulating Mobile Phone,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",7,Adjusting or listening to Portable Audio Device (Other than on a Mobile Phone),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",8,"Adjusting, Talking to, or Manipulating Other Portable Electronic Device",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",12,"Distracted by Animal, Other Object, Event, or Activity",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",13,Eating or Drinking,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",14,Smoking Related,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",15,Other Mobile Phone Related,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",17,Distraction/Inattention,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",18,Distraction/Careless,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",19,Careless/Inattentive,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",92,"Distraction (Distracted), Details Unknown",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",93,"Inattention (Inattentive), Details Unknown",NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",96,Not Reported,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",97,Lost in Thought/Day Dreaming,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",98,Other Distraction (Specify:),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,nmdistract,MNMDSTRD,mnmdstrd,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",99,Reported as Unknown if Distracted,NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",313,CHLORDIAZEPOXIDE,NA,NA,NA,NA,NA,1,1,1,NA,NA
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,PER_NO,per_no,Person Number,"This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files.","Each occupant of the vehicle is numbered, and each non-occupant is numbered; in the case of a non-occupant the vehicle number is zero. The numbers for occupants are consecutive for each vehicle beginning with 1. Numbers are never skipped. Drivers do not have to be coded 1. Non- Occupants are identified by vehicle number 0 and are numbered consecutively starting with 1 for each non-motorist. To get drivers see data element PER_TYP under Person Type. PER_NO can be used in merges, e.g., when merging the FARS person data file with the multiple cause of death file.",NA,(Self-evident),NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,ORDER,order,Order,This data element identifies the order in which the multiple races were listed on the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",NA,(Self-evident),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",0,Not a Fatality (not Applicable),NA,NA,NA,NA,NA,1,1,1,1,NA
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",1,White,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",2,Black or African American,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",3,North American Indian or Alaska Native,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",4,Chinese,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",5,Japanese,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",6,Native Hawaiian,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",7,Filipino,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",18,Asian Indian,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",19,"Other Indian (includes South and Central America, any others, except North American or Asian Indians)",NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",28,Korean,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",38,Samoan,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",48,Vietnamese,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",58,Guamanian or Chamorro,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",68,Other Asian or Pacific Islander,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",78,"Asian or Pacific Islander, no specific (individual) race",NA,NA,NA,NA,NA,1,1,1,1,NA
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",97,Multiple Races Unspecified,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",98,Other Race,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",99,Unknown,NA,NA,NA,NA,NA,1,1,1,1,1
FARS,race,MULTRACE,multrace,Is Multiple Race?,This data element identifies if multiple races were listed on the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",NA,(Self-evident),NA,NA,NA,NA,NA,1,NA,NA,NA,NA
FARS,accident,TYP_INT,typ_int,Type of Intersection,This data element identifies and allows separation of various intersection types.,Prior to 2015 the Data Element ID was C21.,11,Other Intersection Type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",1,Clear,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",2,Rain,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",3,Sleet or Hail,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",4,Snow,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",5,"Fog, Smog, Smoke",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",6,Severe Crosswinds,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",7,"Blowing Sand, Soil, Dirt",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",8,Other,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",10,Cloudy,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",11,Blowing Snow,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",12,Freezing Rain or Drizzle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",98,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",99,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,accident,RAIL,rail,Rail Grade Crossing Identifier,This data element identifies if the crash occurred in or near a rail grade crossing.,Prior to 2015 the Data Element ID was C27.,0,Not Applicable,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,OWNER,owner,Registered Vehicle Owner,This data element identifies the type of registered owner of the vehicle.,This data element also appears in the Parkwork data file as POWNER.,3,Vehicle Registered as Commercial/Business/Company/Government Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",1,American Motors,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",2,Jeep / Kaiser-Jeep / Willys- Jeep,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",3,AM General,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",6,Chrysler,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",7,Dodge,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",8,Imperial,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",9,Plymouth,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",10,Eagle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",12,Ford,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",13,Lincoln,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",14,Mercury,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",18,Buick / Opel,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",19,Cadillac,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",20,Chevrolet,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",21,Oldsmobile,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",22,Pontiac,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",23,GMC,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",24,Saturn,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",25,Grumman,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",26,Coda,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",29,Other Domestic Manufacturers,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",30,Volkswagen,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",31,Alfa Romeo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",32,Audi,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",33,Austin/Austin Healey,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",34,BMW,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",35,Nissan/Datsun,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",36,Fiat,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",37,Honda,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",38,Isuzu,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",39,Jaguar,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",40,Lancia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",41,Mazda,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",42,Mercedes-Benz,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",43,MG,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",44,Peugeot,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",45,Porsche,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",46,Renault,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",47,Saab,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",48,Subaru,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",49,Toyota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",50,Triumph,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",51,Volvo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",52,Mitsubishi,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",53,Suzuki,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",54,Acura,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",55,Hyundai,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",56,Merkur,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",57,Yugo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",58,Infiniti,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",59,Lexus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",60,Daihatsu,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",61,Sterling,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",62,Land Rover,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",63,KIA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",64,Daewoo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",65,Smart,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",67,Scion,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",69,Other Import,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",70,BSA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",71,Ducati,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",72,Harley-Davidson,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",73,Kawasaki,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",74,Moto-Guzzi,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",75,Norton,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",76,Yamaha,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",77,Victory,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",80,Brockway,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",81,Diamond Reo/Reo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",82,Freightliner,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",83,FWD,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",84,International Harvester/Navistar,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",85,Kenworth,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",86,Mack,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",87,Peterbilt,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",88,Iveco/Magirus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",89,White/Autocar White/GMC,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",90,Bluebird,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",91,Eagle Coach,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",92,Gillig,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",93,MCI,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",94,Thomas Built,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",97,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",98,Other Make,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAKE,make,NCSA Make,This data element identifies the make (manufacturer) of this vehicle by NCSA historically.,"Prior to 2020 this data element’s name was ""Vehicle Make"" and the Data Element ID was V9. This data element also appears in the Person data file and in the Parkwork data file as PMAKE.",99,Unknown Make,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MODEL,model,NCSA Model,This data element identifies the NCSA model of this vehicle within a given NCSA make.,"Prior to 2020 this data element’s name was ""Vehicle Model"" and the Data Element ID was V10. This data element also appears in the Person data file and in the Parkwork data file as PMODEL.",NA,(Self-evident),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1001,American Motors Rambler/American,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1002,American Motors Rebel/Matador/Marlin,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1003,American Motors Ambassador,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1004,American Motors Pacer,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1005,American Motors AMX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1006,American Motors Javelin,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1007,American Motors Hornet/Concord,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1008,American Motors Spirit/Gremlin,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1009,American Motors Eagle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1010,American Motors Eagle SX-4,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1398,American Motors Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",1399,American Motors Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2001,Jeep / Kaiser-Jeep / Willys- Jeep Compass,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2401,Jeep / Kaiser-Jeep / Willys- Jeep CJ-2/CJ-3/CJ-4,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2402,Jeep / Kaiser-Jeep / Willys- Jeep CJ-5/CJ-6/CJ-7/CJ-8,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2403,Jeep / Kaiser-Jeep / Willys- Jeep YJ series/Wrangler,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2404,Jeep / Kaiser-Jeep / Willys- Jeep Cherokee (1984-on) (For Grand Cherokee for 2014 on use 02-422.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2405,Jeep / Kaiser-Jeep / Willys- Jeep Liberty,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2406,Jeep / Kaiser-Jeep / Willys- Jeep Commander,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2407,Jeep / Kaiser-Jeep / Willys- Jeep Patriot,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2408,Jeep / Kaiser-Jeep / Willys- Jeep Renegade,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2421,Jeep / Kaiser-Jeep / Willys- Jeep Cherokee (thru 1983),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2422,Jeep / Kaiser-Jeep / Willys- Jeep Grand Cherokee (For 2014 on.  Use model 404 for model years prior to 2013.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2431,Jeep / Kaiser-Jeep / Willys- Jeep Grand Wagoneer,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2481,Jeep / Kaiser-Jeep / Willys- Jeep Pick-up,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2482,Jeep / Kaiser-Jeep / Willys- Jeep Comanche,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2483,Jeep / Kaiser-Jeep / Willys- Jeep Gladiator,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2498,Jeep / Kaiser-Jeep / Willys- Jeep Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2499,Jeep / Kaiser-Jeep / Willys- Jeep Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",2999,Jeep / Kaiser-Jeep / Willys- Jeep Unknown (JEEP),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3401,AM General Dispatcher,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3402,AM General Hummer,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3421,"AM General Hummer (SUV from 1993-2003; see 431 for 2004 on) (for Pickup, see model 481)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3431,AM General Hummer (2004 on; see model 421 for 1993-2003),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3441,AM General MV-1,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3466,AM General Dispatcher,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3481,AM General Hummer (Pickup) (for SUV see model 421 for 1993-2003; see 431 for 2004 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3482,AM General Hummer,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3498,AM General Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3499,AM General Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3884,AM General Medium/Heavy Truck,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3898,AM General Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3983,"AM General Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3988,AM General Other(bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3989,AM General Unknown Bus Type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3998,AM General Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",3999,AM General Unknown (AM GENERAL),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6009,Chrysler Cordoba,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6010,Chrysler New Yorker (thru 78)/ Newport/5th Avenue/Imperial (1979-83) (excludes all FWD),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6014,Chrysler New Yorker/E-Class/Imperial/ Fifth Avenue,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6015,Chrysler Laser,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6016,Chrysler LeBaron,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6017,Chrysler LeBaron GTS/GTC,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6018,Chrysler 200,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6021,Chrysler SRT Viper,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6031,Chrysler TC (Maserati Sport),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6035,Chrysler Conquest,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6041,Chrysler Concorde,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6042,Chrysler LHS,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6043,Chrysler Sebring,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6044,Chrysler Cirrus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6050,Chrysler Executive,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6051,Chrysler 300M/300/300C/300S,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6052,Chrysler PT Cruiser,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6053,"Chrysler Prowler (2002 on)  (1997,1999-01 see Plymouth)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6054,Chrysler Pacifica (Passenger Cars),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6055,Chrysler Crossfire,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6398,Chrysler Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6399,Chrysler Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6421,Chrysler Aspen,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6441,Chrysler Town and Country,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6442,Chrysler Voyager (2000 - 2003; 1984-00 see Plymouth. For 2020 on see 06-444.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6443,Chrysler Pacifica (Light Trucks),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6444,Chrysler Voyager (2020 on. For 2000-2003 see vehicle make 06-442. For 1984-2000 see Plymouth.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6498,Chrysler Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6499,Chrysler Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",6999,Chrysler Unknown (CHRYSLER),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7001,Dodge Dart,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7002,Dodge Coronet/Magnum/ Charger (thru 1978),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7003,Dodge Polara/Monaco/ Royal Monaco,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7004,Dodge Viper,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7005,Dodge Challenger,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7006,Dodge Aspen,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7007,Dodge Diplomat,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7008,Dodge Omni/Charger (1983 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7009,Dodge Mirada,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7010,Dodge St Regis,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7011,Dodge Aries (K),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7012,Dodge 400,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7013,Dodge Rampage (car-based pickup),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7014,Dodge 600,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7015,Dodge Daytona,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7016,Dodge Lancer,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7017,Dodge Shadow,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7018,Dodge Dynasty,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7019,Dodge Spirit,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7020,Dodge Neon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7021,Dodge Magnum,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7024,Dodge Charger,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7025,Dodge Caliber,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7026,Dodge Avenger,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7027,"Dodge Journey (For 2009-2018 only.  For model years 2019 on, see 07-404.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7028,Dodge Challenger (2008 on; for 1970-74 see model 005),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7029,Dodge Dart (2013 on. See model 001 for 1960-1976.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7030,Dodge Barracuda,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7033,Dodge Challenger,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7034,Dodge Colt  (includes 2WD Vista),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7035,Dodge Conquest,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7039,Dodge Stealth,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7040,Dodge Monaco,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7041,Dodge Intrepid,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7042,Dodge Avenger,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7043,Dodge Stratus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7398,Dodge Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7399,Dodge Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7401,Dodge RaiderSport,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7402,Dodge Durango (1998-2003 only; see model 422 for 2004 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7403,Dodge Nitro,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7404,"Dodge Journey (For 2019 on.  For model years 2009-2018, see 07-027.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7421,Dodge Ramcharger,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7422,Dodge Durango (2004 on; see 402 for 1998-2003 models),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7441,Dodge Vista Van,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7442,Dodge Caravan/Grand Caravan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7443,Dodge Ram C/V,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7444,Dodge Promaster City,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7461,Dodge B-Series Van/Ram Van/ Ram Wagon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7462,Dodge Sprinter,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7463,Dodge Ram Promaster,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7470,Dodge Van Derivative,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7471,"Dodge D50, Colt pickup, Ram 50/Ram 100",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7472,Dodge Dakota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7481,"Dodge D, W-Series pickup",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7482,Dodge Ram Pickup,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7498,Dodge Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7499,Dodge Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7850,Dodge Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7870,Dodge Medium/Heavy Van-Based Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7880,"Dodge Medium/Heavy Pickup (pickup-style only - over 10,000 lbs)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7881,Dodge Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7882,Dodge Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7883,Dodge Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7884,Dodge Medium/Heavy -Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,NA
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7890,Dodge Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7898,Dodge Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7981,Dodge Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7988,Dodge Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7989,Dodge Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7998,Dodge Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7999,Dodge Unknown (DODGE),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",8010,Imperial Imperial,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",8398,Imperial Other (automobile,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",8399,Imperial Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9001,Plymouth Valiant/Scamp/Duster (thru 1976),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9002,Plymouth Satellite/Belvedere,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9003,Plymouth Fury (Fury Gran thru `78),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9004,Plymouth Gran Fury (`80 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9005,Plymouth Barracuda,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9006,Plymouth Volare`,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9007,Plymouth Caravelle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9008,Plymouth Horizon/Turismo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9011,Plymouth Reliant (K),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9013,Plymouth Scamp-(car-based p/u),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9017,Plymouth Sundance,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9019,Plymouth Acclaim,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9020,"Plymouth Neon (2002 and on, see Dodge)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9031,Plymouth Cricket,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9032,Plymouth Arrow,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9033,Plymouth Sapporo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9034,Plymouth Champ/Colt import (includes 2WD Vista),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9035,Plymouth Conquest,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9037,Plymouth Laser,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9038,Plymouth Breeze,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9039,"Plymouth Prowler (2002 and on, see Chrysler)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9398,Plymouth Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9399,Plymouth Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9421,Plymouth Trailduster,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9441,Plymouth Vista Van,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9442,"Plymouth Voyager (minivan) (2001 and on, see Chrysler)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9461,Plymouth Van-fullsize (B-series),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9471,Plymouth Arrow pickup (foreign),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9498,Plymouth Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9499,Plymouth Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9998,Plymouth Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",9999,Plymouth Unknown (PLYMOUTH),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10034,Eagle Summit (excludes wagon),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10037,Eagle Talon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10040,Eagle Premier,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10041,Eagle Vision,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10044,Eagle Medallion,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10045,Eagle Summit Wagon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10398,Eagle Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",10399,Eagle Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12001,Ford Falcon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12002,Ford Fairlane,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12003,Ford Mustang/Mustang II,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12004,Ford Thunderbird (all sizes),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12005,Ford LTD II,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12006,Ford LTD/Custom/Galaxy (all sizes),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12007,Ford Ranchero,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12008,Ford Maverick,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12009,Ford Pinto,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12010,Ford Torino/Gran Torino/Elite,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12011,Ford Granada,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12012,Ford Fairmont,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12013,Ford Escort/EXP/ZX2,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12015,Ford Tempo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12016,"Ford Crown Victoria  (For 2011 on, code as vehicle model 398)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12017,Ford Taurus/Taurus X,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12018,Ford Probe,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12021,Ford Five Hundred,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12022,Ford Freestyle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12023,Ford Fusion,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12024,"Ford Edge (For model years 2007-2018 only.  For model years 2019 on, see 12-424.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12025,Ford Flex,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12026,Ford City,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12027,Ford C-Max,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12031,Ford English Ford,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12032,Ford Fiesta,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12033,Ford Festiva,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12034,Ford Laser,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12035,Ford Contour,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12036,Ford Aspire,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12037,Ford Focus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12038,Ford GT,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12398,Ford Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12399,Ford Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12401,"Ford Bronco (thru 1977)/Bronco II/Explorer/Explorer Sport (Explorer for 1990-2018 only.  For model years 2019 on, see 12-425.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12402,Ford Escape,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12403,Ford EcoSport,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12421,Ford Bronco-fullsize (1978-on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12422,Ford Expedition,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12423,Ford Excursion,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12424,"Ford Edge(For 2019 on.  For model years 2007-2018, see 12-024.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12425,Ford Explorer (For 2019 on.  For model years 1990-2018 see 12-401.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12441,Ford Aerostar,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12442,Ford Windstar,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12443,Ford Freestar,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12444,Ford Transit Connect,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12461,Ford E-Series Van/Econoline,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12462,Ford Transit,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12470,Ford Van Derivative,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12471,Ford Ranger,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12472,Ford Courier,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12473,Ford Explorer Sport Trac,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12481,Ford F-Series pickup,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12498,Ford Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12499,Ford Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12850,Ford Motorhome,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12870,Ford Medium/Heavy Van-Based Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12880,"Ford Medium/Heavy Pickup (pickup-style only - over 10,000 lbs)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12881,Ford Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12882,Ford Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12883,Ford Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12884,Ford Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12890,Ford Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12898,Ford Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12981,Ford Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12988,Ford Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12989,Ford Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12998,Ford Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",12999,Ford Unknown (FORD),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13001,Lincoln Continental (thru `81)/ Town Car,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13002,Lincoln Mark,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13005,Lincoln Continental (`82 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13011,Lincoln Versailles,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13012,Lincoln LS,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13013,Lincoln Zephyr/MKZ,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13014,Lincoln MKX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13015,Lincoln MKS,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13016,Lincoln MKT,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13017,Lincoln Continental,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13398,Lincoln Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13399,Lincoln Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13401,Lincoln Aviator,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13402,Lincoln MKC,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13403,Lincoln Corsair,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13421,Lincoln Navigator,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13422,Lincoln Nautilus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13423,Lincoln Aviator,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13481,Lincoln Blackwood,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13482,Lincoln Mark LT,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13498,Lincoln Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13499,Lincoln Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",13999,Lincoln Unknown (LINCOLN),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14002,Mercury Cyclone,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14003,Mercury Capri- domestic (1967 see 008),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14004,Mercury Cougar/XR7 (1967-1997),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14006,Mercury Marquis/Monterey (car version; for van version 2004 on see code 444) /Grand Marquis,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14008,Mercury Comet,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14009,Mercury Bobcat,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14010,Mercury Montego (prior to 1976; for 2005 on see code 020),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14011,Mercury Monarch,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14012,Mercury Zephyr,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14013,Mercury Lynx/LN7,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14015,Mercury Topaz,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14017,Mercury Sable,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14020,Mercury Montego (2005 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14021,Mercury Milan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14031,Mercury Capri-foreign,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14033,Mercury Pantera-foreign,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14036,Mercury Tracer,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14037,Mercury Mystique,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14038,Mercury Cougar (1999 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14039,Mercury Marauder,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14398,Mercury Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14399,Mercury Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14401,Mercury Mountaineer,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14402,Mercury Mariner,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14443,Mercury Villager,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14444,Mercury Monterey (van version; for car version prior to 2004 see code 006),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14498,Mercury Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14499,Mercury Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",14999,Mercury Unknown (MERCURY),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18001,Buick / Opel Special/Skylark,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18002,"Buick / Opel LeSabre/Centurion/ Estate Wagon, Invicta, Custom, Limited, T-Type, Ltd, C.M.I, LE",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18003,"Buick / Opel Electra/Electra 225/ Park Limited, Park Avenue, Ultra, Base",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18004,Buick / Opel Roadmaster,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18005,Buick / Opel Riviera,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18007,Buick / Opel Century,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18008,Buick / Opel Apollo/Skylark,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18010,Buick / Opel Regal (RWD only),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18012,Buick / Opel Skyhawk,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18015,Buick / Opel Skylark (76-85),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18018,Buick / Opel Somerset/Skylark,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18019,Buick / Opel Regal (2011 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18020,Buick / Opel Regal (FWD),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18021,Buick / Opel Reatta,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18022,Buick / Opel LaCrosse,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18023,Buick / Opel Lucerne,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18024,Buick / Opel Enclave (2008-12 model years only.  For 2013 on see model 421.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18025,Buick / Opel Verano,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18026,Buick / Opel Cascada,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18031,Buick / Opel Opel Kadett,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18032,Buick / Opel Opel Manta,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18033,Buick / Opel Opel GT,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18034,Buick / Opel Opel Isuzu,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18398,Buick / Opel Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18399,Buick / Opel Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18401,Buick / Opel Rendezvous,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18402,Buick / Opel Rainier,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18404,Buick / Opel Encore,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18405,Buick / Opel Envision,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18421,Buick / Opel Enclave (2013 on.  See model 024 for 2008-12 model years.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18441,Buick / Opel Terraza,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18498,Buick / Opel Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18499,Buick / Opel Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",18999,Buick / Opel Unknown BUICK,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19003,"Cadillac Deville/Fleetwood,Coupe de Ville, Sedan de Ville, Fleetwood Brougham, Fleetwood 60 Special, d`Elegan",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19004,Cadillac Limousine,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19005,Cadillac Eldorado,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19006,Cadillac Commercial Series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19009,Cadillac Allante`,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19014,Cadillac Seville,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19016,Cadillac Cimarron,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19017,Cadillac Catera,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19018,Cadillac CTS/CTC,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19019,Cadillac XLR,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19020,Cadillac SRX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19021,Cadillac STS,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19022,Cadillac DTS,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19023,Cadillac XTS,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19024,Cadillac ATS,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19025,Cadillac ELR,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19026,Cadillac CT6,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19027,Cadillac CT5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19398,Cadillac Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19399,Cadillac Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19401,Cadillac XT5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19421,Cadillac Escalade/ESV (from 2004 on; see 431 for 2003 only),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19422,Cadillac XT4,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19423,Cadillac XT6,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19431,Cadillac Escalade ESV,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19480,Cadillac Escalade EXT (from 2002 -2006; for 2007 on see 481),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19481,Cadillac Escalade EXT (from 2007 on; see 480 for 2002-2006),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19498,Cadillac Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19499,Cadillac Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19999,Cadillac Unknown CADILLAC,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20001,"Chevrolet Chevelle/Malibu Classic, Councours, Laguna**, S-3, Greenbriar, Estate, 300,SS-396/454, Deluxe",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20002,"Chevrolet Impala/Caprice (For SS from 2014 on, use 20-021.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20004,Chevrolet Corvette,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20006,Chevrolet Corvair,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20007,Chevrolet El Camino,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20008,Chevrolet Nova (-`79),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20009,Chevrolet Camaro,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20010,Chevrolet Monte Carlo (thru `88),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20011,Chevrolet Vega,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20012,Chevrolet Monza,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20013,Chevrolet Chevette,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20015,Chevrolet Citation,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20016,Chevrolet Cavalier,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20017,Chevrolet Celebrity,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20019,Chevrolet Beretta/Corsica,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20020,Chevrolet Lumina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20021,Chevrolet SS (For 2014 on.  For Impala/Caprice SS use model 20-002.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20022,Chevrolet Cobalt,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20023,Chevrolet HHR,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20024,Chevrolet Traverse (2009-2012 only.  For 2013 on see model 423.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20025,Chevrolet Cruze,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20026,Chevrolet Volt,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20027,Chevrolet Caprice PPV,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20028,Chevrolet Sonic,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20029,Chevrolet Spark,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20031,Chevrolet Spectrum,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20032,Chevrolet Nova/Geo Prizm/Prism,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20033,Chevrolet Sprint/Geo Sprint,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20034,Chevrolet Geo Metro/Metro,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20035,Chevrolet Geo Storm,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20036,Chevrolet Monte Carlo (1995 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20037,Chevrolet Malibu/Malibu Maxx,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20038,Chevrolet SSR,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20039,Chevrolet Aveo/Aveo 5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20040,Chevrolet Bolt,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20398,Chevrolet Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20399,Chevrolet Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20401,"Chevrolet S-10 Blazer/TrailBlazer (2002 only; for 2003 on, see 403)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20402,Chevrolet Geo Tracker/Tracker,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20403,"Chevrolet TrailBlazer (2003 on; for 2002 model, see 401)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20404,Chevrolet Equinox,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20405,Chevrolet Captiva,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20406,Chevrolet Trax,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20407,Chevrolet AMER,NA,NA,NA,NA,NA,NA,1,NA,1,NA
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20421,Chevrolet Fullsize Blazer/Tahoe,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20422,Chevrolet Suburban (from 2004 on; see 431 for 1950-2003),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20423,Chevrolet Traverse (2013 on.  For 2009-2012 see model 024.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20431,Chevrolet Suburban (from 1950-2003;see 422 for 2004 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20441,Chevrolet Astro Van,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20442,Chevrolet Lumina APV,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20443,Chevrolet Venture,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20444,Chevrolet Uplander,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20445,Chevrolet City Express,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20461,Chevrolet G-series van,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20466,Chevrolet P-series van,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20470,Chevrolet Van derivative,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20471,Chevrolet S-10/T-10 Pickup,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20472,Chevrolet LUV,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20473,Chevrolet Colorado,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20481,"Chevrolet C, K, R, V-series pickup/Silverado",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20482,Chevrolet Avalanche,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20498,Chevrolet Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20499,Chevrolet Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20850,Chevrolet Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20870,Chevrolet Medium/Heavy Van-Based Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20880,"Chevrolet Medium/Heavy Pickup (pickup-style only - over 10,000 lbs)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20881,Chevrolet Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20882,Chevrolet Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20883,Chevrolet Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20884,Chevrolet Medium/Heavy -Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,NA
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20890,Chevrolet Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20898,Chevrolet Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20981,Chevrolet Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20988,Chevrolet Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20989,Chevrolet Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20998,Chevrolet Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20999,Chevrolet Unknown (CHEVROLET),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21001,Oldsmobile Cutlass (RWD-only),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21002,Oldsmobile Delta 88/LSS,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21003,Oldsmobile Ninety-Eight/Regency,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21005,Oldsmobile Toronado,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21006,Oldsmobile Commercial Series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21012,Oldsmobile Starfire,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21015,Oldsmobile Omega,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21016,Oldsmobile Firenza,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21017,Oldsmobile Ciera,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21018,Oldsmobile Calais,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21020,Oldsmobile Cutlass (FWD),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21021,Oldsmobile Achieva/Alero,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21022,Oldsmobile Aurora,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21023,Oldsmobile Intrigue,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21398,Oldsmobile Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21399,Oldsmobile Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21401,Oldsmobile Bravada,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21441,Oldsmobile Silhouette,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21499,Oldsmobile Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",21999,Oldsmobile Unknown (OLDSMOBILE),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22001,Pontiac Lemans/ Tempest (thru 1970),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22002,Pontiac Bonneville/Catalina/ Parisienne,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22005,Pontiac Fiero,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22008,Pontiac Ventura/GTO,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22009,Pontiac Firebird/Trans AM,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22010,Pontiac Grand Prix (RWD),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22011,Pontiac Astre,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22012,Pontiac Sunbird (thru 1980;1985 on see model 016),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22013,Pontiac T-1000/1000,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22015,Pontiac Phoenix,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22016,Pontiac Sunbird (1985-1994)/J-2000/Sunfire (1995 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22017,Pontiac 6000,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22018,Pontiac Grand AM,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22019,Pontiac G5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22020,Pontiac Grand Prix (FWD),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22022,Pontiac G6,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22023,Pontiac Solstice,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22024,Pontiac G8,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22025,Pontiac G3,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22026,Pontiac G8-ST,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22031,Pontiac Lemans (1988-on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22032,Pontiac Vibe,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22398,Pontiac Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22399,Pontiac Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22401,Pontiac Aztek,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22403,Pontiac Torrent,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22441,Pontiac Trans Sport/ Montana/SV6,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22499,Pontiac Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",22999,Pontiac Unknown (PONTIAC),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23007,GMC Caballero,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23008,GMC Acadia (2007-2012 only.  For 2013 on see model 423.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23399,GMC Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23401,GMC Jimmy/Typhoon/Envoy,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23402,GMC Terrain,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23421,GMC Fullsize Jimmy/Yukon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23422,GMC Suburban/Yukon XL (2004 on; see 431 for 1950- 2003),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23423,GMC Acadia (2013 on. For 2007-2012 see model 008.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23431,GMC Suburban/Yukon XL (2000 on) (1950-2003 only; see 422 for 2004 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23441,GMC Safari (Minivan),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23461,GMC G-series van/Savana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23466,GMC P-series van,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23470,GMC Van derivative,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23471,GMC S15/T15/Sonoma,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23472,GMC Canyon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23481,"GMC C, K, R, V-series pickup/     Sierra",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23498,GMC Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23499,GMC Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23850,GMC Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23870,GMC Medium/Heavy Van-Based Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23880,"GMC Medium/Heavy Pickup (pickup-style only - over 10,000 lbs",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23881,GMC Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23882,GMC Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23883,GMC Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23884,GMC Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23890,GMC Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23898,GMC Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23981,GMC Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23988,GMC Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23989,GMC Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23998,GMC Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",23999,GMC Unknown (GMC),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24001,Saturn SL,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24002,Saturn SC,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24003,Saturn SW,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24004,Saturn EV1/EGV1*,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24005,Saturn LS,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24006,Saturn LW,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24007,Saturn Ion,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24008,Saturn Sky,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24009,Saturn Aura,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24010,Saturn Outlook,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24011,Saturn Astra,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24398,Saturn Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24399,Saturn Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24401,Saturn Vue,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24441,Saturn Relay,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24499,Saturn Unknown (Light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",24999,Saturn Unknown (SATURN),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25401,Grumman LLV,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25441,Grumman Step-in van,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25498,Grumman Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25499,Grumman Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25881,Grumman Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25882,Grumman Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25883,Grumman Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25884,Grumman Medium/Heavy - engine location unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25890,Grumman Medium/Heavy - entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25898,Grumman Other (Medium/Heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25983,"Grumman Bus: Flat front, rear engine",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25988,Grumman Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25989,Grumman Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",25999,Grumman Unknown (GRUMMAN/ GRUMMAN-OLSON),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",26001,Coda Coda,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",26398,Coda Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",26399,Coda Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29001,Other Domestic Manufacturers Studabaker/Avanti,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29002,Other Domestic Manufacturers Checker,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29003,Other Domestic Manufacturers Panoz,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29004,Other Domestic Manufacturers Saleen,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29005,Other Domestic Manufacturers Tesla,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29398,Other Domestic Manufacturers Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",29399,Other Domestic Manufacturers Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30031,Volkswagen Karmann Ghia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30032,Volkswagen Beetle 1300/1500,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30033,Volkswagen Super Beetle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30034,Volkswagen 411/412,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30035,Volkswagen Squareback/Fastback,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30036,Volkswagen Rabbit,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30037,Volkswagen Dasher,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30038,Volkswagen Scirocco,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30040,Volkswagen Jetta/Jetta SportsWagen,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30041,Volkswagen Quantum,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30042,Volkswagen Golf/Cabriolet/Cabrio/GTI/ GLI,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30043,Volkswagen Rabbit Pickup,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30044,Volkswagen Fox,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30045,Volkswagen Corrado,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30046,Volkswagen Passat (CC - 2008 thru 2011; see 052 for 2012 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30047,Volkswagen New Beetle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30048,Volkswagen Phaeton,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30051,Volkswagen Eos,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30052,Volkswagen CC (For 2012 on. See model 046 for 2008-2011.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30053,Volkswagen Arteon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30398,Volkswagen Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30399,Volkswagen Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30401,Volkswagen The Thing (181),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30402,Volkswagen Tiguan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30403,Volkswagen Atlas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30421,Volkswagen Touareg/Tourareg 2,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30441,Volkswagen Vanagon/Camper,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30442,Volkswagen Eurovan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30443,Volkswagen Routan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30498,Volkswagen Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30499,Volkswagen Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30998,Volkswagen Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",30999,Volkswagen Unknown (VOLKSWAGEN),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31031,Alfa Romeo Spider (Spyder),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31032,Alfa Romeo Sports Sedan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31033,Alfa Romeo Sprint/Special,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31034,Alfa Romeo GTV-6,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31035,Alfa Romeo 164 (Alpha 164),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31036,Alfa Romeo 4c,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31037,Alfa Romeo Giulia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31398,Alfa Romeo Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31399,Alfa Romeo Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31401,"Alfa Romeo Stelvio (For 2018 only.  For model years 2019 on, see 31-422.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31422,"Alfa Romeo Stelvio (For 2019 on.  For model year 2018, see 31-401.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31498,Alfa Romeo Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",31999,Alfa Romeo Unknown (ALFA ROMEO),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32031,Audi Super 90,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32032,Audi 100,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32033,Audi Fox,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32034,Audi 4000,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32035,Audi 5000,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32036,Audi 80/90,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32037,Audi 200,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32038,Audi V-8 Quattro,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32039,Audi Coupe Quattro,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32040,Audi S4 (1992-1994; 2000-2011 only. See model 055 for 2012 on)/S6 (1992-1994; 2000-2011 only.  See model 056 for 2013 on.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32041,Audi Cabriolet (1994-1998),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32042,Audi A6,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32043,Audi A4,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32044,Audi A8,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32045,Audi TT/TTS,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32046,Audi S8,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32047,Audi Allroad (2001-05 only.  See 403 for 2013 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32048,Audi A3,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32049,Audi A5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32050,Audi R8,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32051,Audi A7,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32052,Audi S5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32054,Audi RS5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32055,Audi S4 (2012 on only.  See model 040 for 1992-1994; 2000-2011),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32056,Audi S6 (2013 on.  See model 040 for 1992-1994; 2000-2011),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32057,Audi S7,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32058,Audi RS7,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32059,Audi S3,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32060,Audi RS3,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32398,Audi Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32399,Audi Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32401,"Audi Q7 (For 2007-2018 only.  For model years 2019 on, see 32-422.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32402,Audi Q5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32403,Audi Allroad (2013 on.  For 2001-2005 see model 047.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32404,Audi SQ5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32405,Audi Q3,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32406,Audi e-Tron,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32421,Audi Q8,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32422,"Audi Q7 (For 2019 on.  For model years 2007-2018, see 32-401.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32498,Audi Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32499,Audi Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",32999,Audi Unknown (AUDI),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33031,Austin/Austin Healey Marina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33032,Austin/Austin Healey America,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33033,Austin/Austin Healey Healey Sprite,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33034,Austin/Austin Healey Healey 100/3000,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33035,Austin/Austin Healey Mini/Mini Cooper/Mini Moke,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33398,Austin/Austin Healey Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",33399,Austin/Austin Healey Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34031,"BMW 1600, 1800, 2000,2002",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34032,BMW Coupe (before 1975),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34033,BMW Bavarian Sedan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34034,BMW 3-series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34035,BMW 5-series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34036,BMW 6-series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34037,BMW 7-series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34038,BMW 8-series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34039,BMW Z3,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34040,BMW Z8,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34041,BMW V5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34042,BMW Z4,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34043,BMW 1-Series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34044,"BMW X6 (For 2008-2015. For 2016 on, see model 404.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34045,BMW i3,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34046,BMW i8,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34047,BMW 4-Series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34048,BMW 2-Series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34049,BMW X4,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34398,BMW Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34399,BMW Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34401,"BMW X5 (For 2000-16.  For 2017 on, see model 421).",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34402,BMW X3,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34403,BMW X1,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34404,"BMW X6 (For 2016 on. For 2008-2015, see model 044.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34405,BMW X2,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34421,"BMW X5 (For 2017 on. For 2000-16, see model 401)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34422,BMW X7,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34498,BMW Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34499,BMW Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34703,BMW 125-349cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34704,BMW 350-449 cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34705,BMW 450-749cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34706,BMW 750cc and over,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34707,BMW Electric Motorcycle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34709,BMW Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",34999,BMW Unknown (BMW),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35031,Nissan/Datsun F-10,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35032,Nissan/Datsun 200SX/240SX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35033,Nissan/Datsun 210/1200/B210,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35034,"Nissan/Datsun Z-car, ZX",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35035,Nissan/Datsun 310,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35036,Nissan/Datsun 510,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35037,Nissan/Datsun 610,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35038,Nissan/Datsun 710,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35039,Nissan/Datsun 810/Maxima,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35040,Nissan/Datsun Roadster,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35041,Nissan/Datsun 311/411,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35042,Nissan/Datsun Stanza,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35043,Nissan/Datsun Sentra,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35044,Nissan/Datsun Pulsar,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35045,Nissan/Datsun Micra,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35046,Nissan/Datsun NX 1600/2000,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35047,Nissan/Datsun Altima,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35048,Nissan/Datsun 350Z/370Z,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35049,"Nissan/Datsun Murano (For 2003-2018 only.  For model years 2019 on, see 35-422.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35050,Nissan/Datsun Versa,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35051,"Nissan/Datsun Rogue (For 2008-2018 only.  For model years 2019 on, see 35-404.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35052,Nissan/Datsun Cube,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35053,Nissan/Datsun GT-R,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35055,Nissan/Datsun Leaf,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35056,Nissan/Datsun Kicks,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35398,Nissan/Datsun Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35399,Nissan/Datsun Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35401,Nissan/Datsun Pathfinder,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35402,Nissan/Datsun Xterra,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35403,Nissan/Datsun Juke,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35404,"Nissan/Datsun Rogue (For 2019 on.  For model years 2008-2018, see 35-051.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35421,Nissan/Datsun Pathfinder Armada,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35422,"Nissan/Datsun Murano (For 2019 on.  For model years 2003-2018, see 35-056.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35441,Nissan/Datsun Van,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35442,Nissan/Datsun Axxess,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35443,Nissan/Datsun Quest,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35444,Nissan/Datsun Altra EV*,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35446,Nissan/Datsun NV200/eNV200,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35461,Nissan/Datsun NV,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35471,Nissan/Datsun Nissan/Datsun Pickup (1955-1997),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35472,Nissan/Datsun Frontier (1998 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35473,Nissan/Datsun Titan (from 2004-06; see 481 for 2007 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35481,Nissan/Datsun Titan (from 2007 on; see 473 for 2004-06),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35498,Nissan/Datsun Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35499,Nissan/Datsun Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35870,Nissan/Datsun Medium Heavy Van-Based Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35883,NA,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35898,Nissan/Datsun Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35999,Nissan/Datsun Unknown (NISSAN/DATSUN),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36031,Fiat 124 (Coupe/Sedan),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36032,Fiat 124 Spider/Racer,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36033,Fiat Brava/131,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36034,Fiat 850 (Coupe/Spider),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36035,Fiat 128,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36036,Fiat X-1/9,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36037,Fiat Strada,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36038,Fiat 500/500c,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36039,Fiat 124 Spider,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36398,Fiat Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36399,Fiat Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36401,Fiat 500L,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36402,Fiat 500X,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36498,Fiat Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36499,Fiat Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36882,Fiat Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36883,Fiat Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36890,Fiat Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36898,Fiat Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36998,Fiat Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",36999,Fiat Unknown (FIAT),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37031,"Honda Civic/CRX, del Sol",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37032,"Honda Accord (Note: For Crosstour model years 2010 and 2011 only. For Crosstour model years 2012-2015, see vehicle model 37-405)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37033,Honda Prelude,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37034,Honda 600,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37035,Honda S2000,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37036,Honda EV Plus*,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37037,Honda Insight,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37038,Honda FCX/Clarity,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37039,Honda Fit,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37041,Honda CR-Z,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37398,Honda Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37399,Honda Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37401,Honda Passport,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37402,Honda CR-V,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37403,Honda Element,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37404,Honda HR-V,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37405,Honda Crosstour (2012-2015 only. See vehicle model 37-032 for model years 2010 and 2011.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37421,Honda Pilot,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37422,Honda Passport (2019 on. For 1994-2002 see model 401.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37441,Honda Odyssey,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37471,Honda Ridgeline,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37498,Honda Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37499,Honda Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37701,Honda 0- 50 cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37702,Honda 51-124 cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37703,Honda 125-349 cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37704,Honda 350-449 cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37705,Honda 450-749 cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37706,Honda 750 cc or greater,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37709,Honda Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37732,Honda 51-124cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37733,Honda 125-349cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37734,Honda 350cc or greater (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37739,Honda Unknown cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37998,Honda (Other Vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",37999,Honda Unknown (HONDA),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38031,Isuzu I-Mark,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38032,Isuzu Impulse,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38033,Isuzu Stylus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38398,Isuzu Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38399,Isuzu Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38401,Isuzu Trooper/Trooper II,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38402,Isuzu Rodeo/ Rodeo Sport,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38403,Isuzu Amigo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38404,Isuzu VehiCROSS,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38405,Isuzu Axiom,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38421,Isuzu Ascender,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38441,Isuzu Oasis,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38471,Isuzu P`up (pickup),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38472,Isuzu Hombre,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38473,Isuzu i-280/i-290,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38474,Isuzu i-350/i-370,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38498,Isuzu Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38499,Isuzu Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38881,Isuzu Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38882,"Isuzu Medium/Heavy - COE, low entry",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38883,"Isuzu Medium/Heavy - COE, high entry",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38884,Isuzu Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38890,Isuzu Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38898,Isuzu Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38981,Isuzu Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38982,"Isuzu Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38983,Isuzu Bus: Rear engine Flat front,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38988,Isuzu Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38989,Isuzu Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",38999,Isuzu Unknown (ISUZU),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39031,"Jaguar XJ-S, XK8 Coupe",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39032,Jaguar XJ/XJL/XJ6/12/XJR/XJ8/  XJ8L Sedan/Coupe,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39033,Jaguar XK-E,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39034,Jaguar S-Type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39035,Jaguar XKR/XK,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39036,Jaguar X-Type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39037,Jaguar XF/XFR,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39038,Jaguar F-Type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39039,Jaguar XE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39398,Jaguar Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39399,Jaguar Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39401,Jaguar F-Pace,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39402,Jaguar E-Pace,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39403,Jaguar I-Pace,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39498,Jaguar Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39499,Jaguar Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",39999,Jaguar Unknown (JAGUAR),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",40031,Lancia Beta Sedan - HPE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",40032,Lancia Zagato,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",40033,Lancia Scorpion,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",40398,Lancia Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",40399,Lancia Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41031,Mazda RX2,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41032,Mazda RX3,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41033,Mazda RX4,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41034,Mazda RX7,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41035,NA,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41036,Mazda Cosmo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41037,Mazda 626,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41038,Mazda 808,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41039,Mazda Mizer,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41040,Mazda R-100,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41041,Mazda 616/618,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41042,Mazda 1800,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41043,Mazda 929,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41044,Mazda MX-6,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41045,Mazda Miata/MX-5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41046,Mazda MX-3,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41047,Mazda Millenia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41048,Mazda MP3,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41049,Mazda RX-8,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41050,Mazda Mazda6,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41051,Mazda Mazda3,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41052,Mazda Mazda5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41053,Mazda CX-7,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41054,Mazda CX-9 (2007-12 only.For 2013 on see model 421.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41055,Mazda Mazda2,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41056,Mazda CX-3,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41398,Mazda Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41399,Mazda Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41401,Mazda Navajo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41402,Mazda Tribute,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41403,Mazda CX5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41421,Mazda CX-9 (2013 on. See model 054 for 2007-12 model years.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41441,Mazda MPV,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41471,Mazda Pickup/ B-Series Pickup,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41498,Mazda Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41499,Mazda Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41999,Mazda Unknown (MAZDA),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42031,Mercedes-Benz 200/220/230/240/ 250/260/280/300/ 320/420,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42032,Mercedes-Benz 230/280 SL,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42033,Mercedes-Benz 300/350/380/450/500/ 560 SL,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42034,Mercedes-Benz 350/380/420/450/560 SLC,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42035,Mercedes-Benz 280/300 SEL,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42036,"Mercedes-Benz 300/380/420/450/500/560/SEL & 500/560, 600 SEC & 300/350 SDL",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42037,Mercedes-Benz 300/380/450 SE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42038,"Mercedes-Benz 600, 6.9 Sedan",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42039,Mercedes-Benz 190,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42040,Mercedes-Benz 300,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42041,Mercedes-Benz 400/500E,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42042,Mercedes-Benz C Class (94 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42043,Mercedes-Benz S Class (95 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42044,Mercedes-Benz SL Class (95 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42045,Mercedes-Benz SLK,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42046,Mercedes-Benz CL Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42047,Mercedes-Benz CLK,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42048,Mercedes-Benz E Class (97 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42049,Mercedes-Benz SLR,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42050,Mercedes-Benz R Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42051,Mercedes-Benz CLS Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42052,Mercedes-Benz SLS Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42053,Mercedes-Benz B Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42054,Mercedes-Benz CLA Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42055,Mercedes-Benz GLA Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42056,Mercedes-Benz AMG GT S,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42057,Mercedes-Benz SLC Series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42058,Mercedes-Benz A-Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42398,Mercedes-Benz Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42399,Mercedes-Benz Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42401,Mercedes-Benz M/ML Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42402,Mercedes-Benz G Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42403,Mercedes-Benz GLK Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42404,"Mercedes-Benz GLE Class (For 2016-2018 only.  For model years 2019 on, see 42-423.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42405,Mercedes-Benz GLC Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42406,Mercedes-Benz GLB Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42421,Mercedes-Benz GL Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42422,Mercedes-Benz GLS Class,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42423,"Mercedes-Benz GLE Class (For 2019 on.  For model years 2016-2018, see 42-404.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42461,Mercedes-Benz SPRINTER,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42462,Mercedes-Benz Metris,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42470,Mercedes-Benz Van derivative,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42498,Mercedes-Benz Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42499,Mercedes-Benz Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42850,Mercedes-Benz Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42870,Mercedes-Benz Medium Heavy Van-Based Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42881,Mercedes-Benz Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42882,Mercedes-Benz Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42883,Mercedes-Benz Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42884,Mercedes-Benz Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42890,Mercedes-Benz Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42898,Mercedes-Benz Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42981,Mercedes-Benz Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42988,Mercedes-Benz Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42989,Mercedes-Benz Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42998,Mercedes-Benz Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",42999,Mercedes-Benz Unknown (MERCEDES-BENZ),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43031,MG Midget,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43032,MG MGB,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43033,MG MGB,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43034,MG MGA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43035,MG TA/TC/TD/TF,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43036,MG MGC,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43037,MG Magnette/Sports Sedans,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43398,MG Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",43399,MG Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44031,Peugeot 304,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44032,Peugeot 403,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44033,Peugeot 404,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44034,Peugeot 504/505,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44035,Peugeot 604,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44036,Peugeot 405,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44398,Peugeot Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44399,Peugeot Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44701,Peugeot 0 - 50 cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44702,Peugeot 51-124cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44709,Peugeot Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",44999,Peugeot Unknown (PEUGEOT),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45031,Porsche 911/996,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45032,Porsche 912,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45033,Porsche 914,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45034,Porsche 924,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45035,Porsche 928,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45036,Porsche 930,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45037,Porsche 944,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45038,Porsche 959,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45039,Porsche 968,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45040,Porsche 986/Boxster,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45041,Porsche Cayman,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45042,Porsche Panamera,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45043,Porsche 918,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45044,Porsche 718,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45045,Porsche Taycan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45398,Porsche Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45399,Porsche Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45401,Porsche Macan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45421,Porsche Cayenne,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45498,Porsche Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45499,Porsche Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",45999,Porsche Unknown(PORSCHE),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46031,Renault LeCar,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46032,Renault Dauphine/10/R-8 Caravelle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46033,Renault 12,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46034,Renault 15,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46035,Renault 16,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46036,Renault 17,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46037,Renault 18i/Sportwagon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46038,Renault Fuego,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46039,"Renault Alliance/Encore GTA, Convertible",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46041,Renault Alpine,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46044,Renault Medallion **,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46045,Renault Premier**,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46398,Renault Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",46399,Renault Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47031,Saab 99/99E/900,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47032,Saab Sonnett,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47033,Saab 95/96,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47034,Saab 9000,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47035,Saab 9-3/9-3X,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47036,Saab 9-5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47037,Saab 9-2X,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47038,Saab 9-4X,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47398,Saab Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47399,Saab Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47401,Saab 9-7x,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",47999,Saab Unknown(SAAB),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48031,Subaru Loyale (1990 on)/DL/ FE/G/GF/GL/GLF/STD,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48032,Subaru Star,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48033,Subaru 360,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48034,Subaru Legacy/Outback(prior to 2003 only; see 045 for 2003 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48035,Subaru XT/XT6,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48036,Subaru Justy,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48037,Subaru SVX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48038,Subaru Impreza,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48039,Subaru RX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48043,Subaru Brat,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48044,Subaru Baja,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48045,Subaru Outback (2003 on)(see 034 for prior to 2003),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48046,Subaru BRZ,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48047,Subaru WRX (2015 on; see 038 for prior to 2015.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48398,Subaru Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48399,Subaru Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48401,Subaru Forester,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48402,Subaru B9 Tribeca,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48403,Subaru XV Crosstrek,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48421,Subaru Ascent,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48498,Subaru Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48499,Subaru Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",48999,Subaru Unknown (SUBARU),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49031,Toyota Corona,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49032,Toyota Corolla,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49033,Toyota Celica,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49034,Toyota Supra,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49035,Toyota Cressida,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49036,Toyota Crown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49037,Toyota Carina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49038,Toyota Tercel,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49039,Toyota Starlet,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49040,Toyota Camry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49041,Toyota MR-2/MR Spyder,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49042,Toyota Paseo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49043,Toyota Avalon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49044,Toyota Solara,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49045,Toyota ECHO,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49046,Toyota Prius *,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49047,Toyota Matrix,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49048,Toyota Scion xA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49049,Toyota Scion xB (2004-2011 only.  See Scion for 2012 on.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49050,Toyota Scion tC (2005-2011 only.  See Scion for 2012 on.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49051,Toyota Yaris,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49052,Toyota Scion xD (2007-2011 only.  See Scion for 2012 on.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49053,Toyota Venza,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49054,Toyota Scion iQ (2010-2011 only.  See Scion for 2012 on.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49055,Toyota Mirai,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49056,Toyota 86,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49057,Toyota GR Supra,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49398,Toyota Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49399,Toyota Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49401,Toyota 4-Runner,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49402,Toyota RAV4 *,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49403,Toyota Highlander,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49404,Toyota FJ Cruiser,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49405,Toyota C-HR,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49421,Toyota Land Cruiser,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49422,Toyota Sequoia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49441,Toyota Minivan (1984-90)/ Previa (1991 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49442,Toyota Sienna,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49471,Toyota Pickup,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49472,Toyota Tacoma,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49481,Toyota T-100,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49482,Toyota Tundra,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49498,Toyota Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49499,Toyota Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",49999,Toyota Unknown (TOYOTA),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50031,Triumph Spitfire,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50032,Triumph GT-6,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50033,Triumph TR4,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50034,Triumph TR6,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50035,Triumph TR7/TR8,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50036,Triumph Herald,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50037,Triumph Stag,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50398,Triumph Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50399,Triumph Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50701,Triumph 0-50cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50702,Triumph 51-124cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50703,Triumph 125-349cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50704,Triumph 350-449cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50705,Triumph 450-749cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50706,Triumph 750cc or greater,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50709,Triumph Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50799,Triumph Unknown (motored cycle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",50999,Triumph Unknown (TRIUMPH),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51031,Volvo 122,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51032,Volvo 140/142/144/145 *,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51033,Volvo 164,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51034,Volvo 240 series*/DL/GL/GLT,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51035,Volvo 260 series/GLE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51036,Volvo 1800,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51037,Volvo PV544,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51038,Volvo 760/780,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51039,Volvo 740,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51040,Volvo 940,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51041,Volvo 960,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51042,Volvo 850,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51043,"Volvo 70 Series (For XC70 for 2014 on, use model code 402)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51044,Volvo 90 Series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51045,Volvo 80 Series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51046,Volvo 40 Series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51047,Volvo 60 Series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51048,Volvo V50,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51049,Volvo C30,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51050,"Volvo XC60 (For 2008-2018 only.  For model years 2019 on, see 51-404.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51051,Volvo V60,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51052,Volvo V90,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51053,Volvo S90,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51398,Volvo Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51399,Volvo Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51401,Volvo XC90,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51402,"Volvo XC70 (For 2014 on.  For prior to 2013, use model code 043)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51403,Volvo XC40,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51404,"Volvo XC60 (For 2019 on.  For model years 2008-2018, see 51-050.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51498,Volvo Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51499,Volvo Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51881,Volvo Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51882,Volvo Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51883,Volvo Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51884,Volvo Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51890,Volvo Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51898,Volvo Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51981,Volvo Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51983,"Volvo Bus : Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51988,Volvo Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51989,Volvo Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51998,Volvo Other (Vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",51999,Volvo Unknown (VOLVO),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52031,Mitsubishi Starion,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52032,Mitsubishi Tredia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52033,Mitsubishi Cordia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52034,Mitsubishi Galant,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52035,Mitsubishi Mirage (For 1985-2002.  For 2014 on use model 048.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52036,Mitsubishi Precis,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52037,Mitsubishi Eclipse,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52038,Mitsubishi Sigma,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52039,Mitsubishi 3000 GT,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52040,Mitsubishi Diamante,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52041,"Mitsubishi iMiEV  (For 2018 on, code as vehicle model 398)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52045,Mitsubishi Expo Wagon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52046,Mitsubishi Lancer/Lancer Sportback/ Lancer Evolution,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52047,"Mitsubishi Outlander (For 2003-2018 only.  For model years 2019 on, see 52-404.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52048,Mitsubishi Mirage (2014 on.  For 1985-2002 use 52-035.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52398,Mitsubishi Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52399,Mitsubishi Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52401,Mitsubishi Montero/Montero Sport,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52402,Mitsubishi Endeavor,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52403,Mitsubishi Eclipse Cross,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52404,"Mitsubishi Outlander (For 2019 on.  For model years 2003-2018, see 52-047.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52441,Mitsubishi Mini-Van,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52471,Mitsubishi Pickup,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52472,Mitsubishi Raider,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52498,Mitsubishi Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52499,Mitsubishi Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52882,"Mitsubishi Medium/Heavy - COE, low entry",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52898,Mitsubishi Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52981,Mitsubishi Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52982,"Mitsubishi Bus: Front engine, Flat Front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52983,"Mitsubishi Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52988,Mitsubishi Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52989,Mitsubishi Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",52999,Mitsubishi Unknown (MITSUBISHI),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53031,Suzuki Swift/SA310,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53032,Suzuki Esteem,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53033,Suzuki Aerio,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53034,Suzuki Forenza,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53035,Suzuki Verona,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53036,Suzuki Reno,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53040,Suzuki SX4/SX4 Crossover,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53041,Suzuki Kizashi,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53398,Suzuki Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53399,Suzuki Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53401,Suzuki Samurai,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53402,Suzuki Sidekick/Vitara/ Vitara V6,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53403,Suzuki X-90,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53404,Suzuki Grand Vitara (2003 on; see model 402 for models prior to 2003),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53405,Suzuki XL-7 (2003 on; see 402 for 2002 model year),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53481,Suzuki Equator,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53498,Suzuki Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53499,Suzuki Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53701,Suzuki 0-50cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53702,Suzuki 51-124cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53703,Suzuki 125-349cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53704,Suzuki 350-449cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53705,Suzuki 450-749cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53706,Suzuki 750cc-over,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53709,Suzuki Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53731,Suzuki 0-50cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53732,Suzuki 51-124cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53733,Suzuki 125-349cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53734,Suzuki 350cc or greater (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53739,Suzuki Unknown cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",53999,Suzuki Unknown (SUZUKI),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54031,Acura Integra,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54032,Acura Legend,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54033,Acura NSX (For 1991-2005 only.  For 2016 on see model 043.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54034,Acura Vigor,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54035,Acura TL,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54036,Acura RL/RLX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54037,Acura CL,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54038,Acura RSX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54039,Acura TSX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54040,Acura ZDX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54041,Acura ILX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54043,Acura NSX (2016 on.  For 1991-2005 see model 033.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54044,Acura TLX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54398,Acura Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54399,Acura Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54401,Acura SLX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54402,Acura RDX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54421,Acura MDX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54498,Acura Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54499,Acura Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",54999,Acura Unknown (ACURA),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55031,Hyundai Pony,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55032,Hyundai Excel,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55033,Hyundai Sonata,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55034,Hyundai Scoupe,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55035,Hyundai Elantra,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55036,Hyundai Accent,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55037,Hyundai Tiburon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55038,Hyundai XG300(2001)/ XG350(2002 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55039,"Hyundai Azera  (For 2018 on, code as vehicle model 398)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55040,Hyundai Equus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55041,"Hyundai Genesis (For 2009-2016 only. For model years 2017 on, see 55-043, 55-044 and 55-046)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55042,Hyundai Veloster,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55043,Hyundai Genesis (G80),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55044,Hyundai Genesis (G90),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55045,Hyundai Ioniq,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55046,Hyundai Genesis (G70),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55398,Hyundai Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55399,Hyundai Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55401,Hyundai Santa Fe,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55402,Hyundai Tucson,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55403,Hyundai Veracruz (2007 only),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55404,Hyundai Kona,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55405,Hyundai Nexo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55406,Hyundai Venue,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55421,Hyundai Veracruz  (2008 on; see 403 for 2007 only),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55422,Hyundai Palisade,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55441,Hyundai Entourage,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55498,Hyundai Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55499,Hyundai Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55999,Hyundai Unknown (HYUNDAI),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",56031,Merkur XR4Ti,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",56032,Merkur Scorpio,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",56398,Merkur Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",56399,Merkur Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",57031,Yugo GV/GVL/GVX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58031,Infiniti M30,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58032,Infiniti Q45,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58033,Infiniti G20,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58034,Infiniti J30,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58035,Infiniti I30,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58036,Infiniti I35,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58037,Infiniti G25/G35/G37,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58038,Infiniti M35/M37/M45/M56,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58039,Infiniti FX35/FX37/FX45/FX50,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58040,Infiniti EX35/EX37,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58041,Infiniti Q50,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58042,Infiniti Q60,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58043,Infiniti Q70,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58044,Infiniti QX50,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58045,Infiniti Q40,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58047,Infiniti QX30,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58398,Infiniti Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58399,Infiniti Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58401,Infiniti QX4,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58402,Infiniti JX35,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58403,Infiniti QX60,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58404,Infiniti QX70,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58421,Infiniti QX56,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58422,Infiniti QX80,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58498,Infiniti Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58499,Infiniti Unknown (Light Truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",58999,Infiniti Unknown (INFINITI),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59031,Lexus ES-250/300/300h/330/ 350,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59032,Lexus LS-400/430/460/460L/600h/600hL,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59033,Lexus SC-400/SC-300,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59034,Lexus GS-300/350/400/430/ 450h/460,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59035,Lexus IS-250/300/350/500/200t,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59036,Lexus SC-430,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59037,Lexus HS 250h,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59038,Lexus CT 200h,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59039,Lexus LFA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59040,Lexus RC,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59042,Lexus LC Series,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59043,Lexus UX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59398,Lexus Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59399,Lexus Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59401,Lexus RX300/350,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59402,Lexus GX470,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59403,Lexus RX330/350/400h/450h,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59404,Lexus GX460,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59405,Lexus NX,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59421,Lexus LX450/470/570,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59498,Lexus Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59499,Lexus Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",59999,Lexus Unknown (LEXUS),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",60031,Daihatsu Charade,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",60401,Daihatsu Rocky,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",60999,Daihatsu Unknown (DAIHATSU),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",61031,Sterling 827,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",61398,Sterling Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",61399,Sterling Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62401,"Land Rover Discovery (For 2017 on, see model 425)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62402,Land Rover Defender,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62403,Land Rover Freelander (2004 on; see 422 for 2002-03.),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62404,Land Rover Range Rover Evoque,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62405,Land Rover Discovery Sport,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62421,Land Rover Range Rover,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62422,Land Rover Freelander (2002-03 only; see 403 for 2004 on),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62423,Land Rover LR3/LR4,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62424,Land Rover LR2,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62425,"Land Rover Discovery (For model years 1994-2004, see model 401)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62426,Land Rover Velar,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62427,Land Rover Defender,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62498,Land Rover Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",62499,Land Rover Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63031,KIA Sephia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63032,KIA Rio/Rio5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63033,KIA Spectra/Spectra5,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63034,KIA Optima,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63035,KIA Amanti,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63036,KIA Rondo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63037,KIA Soul,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63038,KIA Forte,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63039,KIA Cadenza,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63040,KIA K900,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63041,KIA Stinger,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63398,KIA Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63399,KIA Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63401,KIA Sportage,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63402,KIA Sorento,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63403,KIA Niro,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63421,KIA Borrego,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63422,KIA Telluride,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63441,KIA Sedona,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63498,KIA Other (Light Truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63499,KIA Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",63999,KIA Unknown (KIA),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",64031,Daewoo Lanos,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",64032,Daewoo Nubira,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",64033,Daewoo Leganza,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",64398,Daewoo Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",64399,Daewoo Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",65031,Smart Fortwo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",65398,Smart Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",65399,Smart Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67031,Scion xB (2012 on.  See Toyota for 2004-2011),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67032,Scion tC (2012 on.  See Toyota for 2005-2011),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67033,Scion xD (2012 on.  See Toyota for 2007-2011),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67034,Scion iQ (2012 on.  See Toyota for 2010-2011),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67035,Scion FR-S,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67036,Scion iA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67037,Scion iM,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67398,Scion Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",67399,Scion Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69031,Other Import Aston Martin,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69032,Other Import Bricklin,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69033,Other Import Citroen,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69034,Other Import DeLorean,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69035,Other Import Ferrari,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69036,Other Import Hillman,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69037,Other Import Jensen,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69038,Other Import Lamborghini,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69039,Other Import Lotus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69040,Other Import Maserati,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69041,Other Import Morris,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69042,Other Import Rolls Royce/Bentley,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69044,Other Import Simca,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69045,Other Import Sunbeam,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69046,Other Import TVR,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69048,Other Import Desta,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69049,Other Import Reliant,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69052,Other Import Bertone,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69053,Other Import Lada,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69054,Other Import Mini-Cooper,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69055,Other Import Morgan (2003 on; Prior to 2003 see 398),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69056,Other Import Maybach,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69057,Other Import Spyker,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69058,Other Import Koenigsegg,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69061,Other Import Mahindra,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69062,Other Import Caterham,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69063,Other Import McLaren,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69064,Other Import Bugatti,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69398,Other Import Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",69399,Other Import Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70701,BSA 0-50cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70702,BSA 51-124cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70703,BSA 125-349cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70704,BSA 350-449cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70705,BSA 450-749cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70706,BSA 750cc or greater,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",70709,BSA Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71701,Ducati 0-50cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71702,Ducati 51-124cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71703,Ducati 125-349cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71704,Ducati 350-449cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71705,Ducati 450-749cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71706,Ducati 750cc or greater,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",71709,Ducati Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72701,Harley-Davidson 0-50cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72702,Harley-Davidson 51-124cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72703,Harley-Davidson 125-349cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72704,Harley-Davidson 350-449cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72705,Harley-Davidson 450-749cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72706,Harley-Davidson 750cc or greater,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72707,Harley-Davidson Electric Motorcycle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",72709,Harley-Davidson Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73701,Kawasaki 0-50cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73702,Kawasaki 51-124cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73703,Kawasaki 125-349cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73704,Kawasaki 350-449cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73705,Kawasaki 450-749cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73706,Kawasaki 750cc or greater,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73709,Kawasaki Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73731,Kawasaki 0-50cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73732,Kawasaki 51-124cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73733,Kawasaki 125-349cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73734,Kawasaki 350cc or greater (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73739,Kawasaki Unknown cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73998,Kawasaki Other (Vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",74704,Moto-Guzzi 350-449cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",74705,Moto-Guzzi 450-749cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",74706,Moto-Guzzi 750cc or greater,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",74709,Moto-Guzzi Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",75704,Norton 350-449cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",75705,Norton 450-749cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",75706,Norton 750cc or greater,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",75709,Norton Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76701,Yamaha 0-50cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76702,Yamaha 51-124cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76703,Yamaha 125-349cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76704,Yamaha 350-449cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76705,Yamaha 450-749cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76706,Yamaha 750cc or greater,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76709,Yamaha Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76731,Yamaha 0-50cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76732,Yamaha 51-124cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76733,Yamaha 125-349cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76734,Yamaha 350cc or greater (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76739,Yamaha Unknown cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",76998,Yamaha Other (Vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",77706,Victory 750cc or greater,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",77707,Victory Electric Motorcycle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",77709,Victory Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",77998,Victory Other (Vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80850,Brockway Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80881,Brockway Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80882,Brockway Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80883,Brockway Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80884,Brockway Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80890,Brockway Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80898,Brockway Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80981,Brockway Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80982,"Brockway Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80983,"Brockway Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80988,Brockway Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80989,Brockway Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80998,Brockway Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",80999,Brockway Unknown (BROCKWAY),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81850,Diamond Reo/Reo Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81881,Diamond Reo/Reo Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81882,Diamond Reo/Reo Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81883,Diamond Reo/Reo Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81884,Diamond Reo/Reo Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81890,Diamond Reo/Reo Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81898,Diamond Reo/Reo Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81981,Diamond Reo/Reo Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81982,"Diamond Reo/Reo Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81983,"Diamond Reo/Reo Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81988,Diamond Reo/Reo Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81989,Diamond Reo/Reo Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81998,Diamond Reo/Reo Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",81999,Diamond Reo/Reo Unknown (DIAMOND REO or REO),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82461,Freightliner Sprinter/Advantage,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82462,Freightliner MT 35 Chassis,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82498,Freightliner Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82499,Freightliner Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82850,Freightliner Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82870,Freightliner Medium Heavy Van-Based Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82881,Freightliner Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82882,Freightliner Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82883,Freightliner Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82884,Freightliner Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82890,Freightliner Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82898,Freightliner Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82981,Freightliner Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82982,"Freightliner Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82983,"Freightliner Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82988,Freightliner Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82989,Freightliner Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82998,Freightliner Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",82999,Freightliner Unknown (FREIGHTLINER),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83850,FWD Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83881,FWD Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83882,FWD Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83883,FWD Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83884,FWD Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83890,FWD Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83898,FWD Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83981,FWD Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83982,"FWD Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83983,"FWD Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83988,FWD Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83989,FWD Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83998,FWD Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",83999,FWD Unknown (FWD),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84421,International Harvester/Navistar Scout,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84431,International Harvester/Navistar Travelall,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84466,International Harvester/Navistar Multistop Van,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84481,International Harvester/Navistar Pickup,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84498,International Harvester/Navistar Other light truck,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84499,International Harvester/Navistar Unknown light truck,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84850,International Harvester/Navistar Motorhome,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84881,International Harvester/Navistar Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84882,International Harvester/Navistar Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84883,International Harvester/Navistar Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84884,International Harvester/Navistar Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84890,International Harvester/Navistar Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84898,International Harvester/Navistar Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84981,International Harvester/Navistar Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84982,"International Harvester/Navistar Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84983,"International Harvester/Navistar Bus**: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84988,International Harvester/Navistar Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84989,International Harvester/Navistar Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84998,International Harvester/Navistar Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",84999,International Harvester/Navistar Unknown (INTL. HARVESTER/ NAVISTAR),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85850,Kenworth Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85881,Kenworth Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85882,Kenworth Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85883,Kenworth Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85884,Kenworth Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85890,Kenworth Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85898,Kenworth Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85981,Kenworth Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85982,"Kenworth Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85983,"Kenworth Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85988,Kenworth Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85989,Kenworth Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85998,Kenworth Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",85999,Kenworth Unknown (KENWORTH),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86850,Mack Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86881,Mack Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86882,Mack Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86883,Mack Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86884,Mack Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86890,Mack Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86898,Mack Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86981,Mack Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86982,"Mack Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86983,"Mack Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86988,Mack Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86989,Mack Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86998,Mack Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",86999,Mack Unknown (MACK),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87850,Peterbilt Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87881,Peterbilt Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87882,Peterbilt Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87883,Peterbilt Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87884,Peterbilt Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87890,Peterbilt Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87898,Peterbilt Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87981,Peterbilt Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87982,"Peterbilt Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87983,"Peterbilt Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87988,Peterbilt Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87989,Peterbilt Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87998,Peterbilt Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",87999,Peterbilt Unknown (PETERBILT),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88850,Iveco/Magirus Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88881,Iveco/Magirus Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88882,Iveco/Magirus Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88883,Iveco/Magirus Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88884,Iveco/Magirus Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88890,Iveco/Magirus Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88898,Iveco/Magirus Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88981,Iveco/Magirus Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88982,"Iveco/Magirus Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88983,"Iveco/Magirus Bus: Rear engine,Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88988,Iveco/Magirus Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88989,Iveco/Magirus Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88998,Iveco/Magirus Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",88999,Iveco/Magirus Unknown (IVECO/MAGIRUS),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89850,White/Autocar White/GMC Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89881,White/Autocar White/GMC Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89882,White/Autocar White/GMC Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89883,White/Autocar White/GMC Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89884,White/Autocar White/GMC Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89890,White/Autocar White/GMC Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89898,White/Autocar White/GMC Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89981,White/Autocar White/GMC Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89982,"White/Autocar White/GMC Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89983,"White/Autocar White/GMC Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89988,White/Autocar White/GMC Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89989,White/Autocar White/GMC Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89998,White/Autocar White/GMC Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",89999,White/Autocar White/GMC Unknown (WHITE/AUTOCAR-WHITE/GMC),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90461,Bluebird Van Based,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90981,Bluebird Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90982,"Bluebird Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90983,"Bluebird Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90988,Bluebird Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90989,Bluebird Unknown (Bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",90999,Bluebird Unknown (BLUEBIRD),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",91981,Eagle Coach Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",91982,"Eagle Coach Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",91983,"Eagle Coach Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",91988,Eagle Coach Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",91989,Eagle Coach Unknown (Bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",92981,Gillig Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",92982,"Gillig Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",92983,"Gillig Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",92988,Gillig Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",92989,Gillig Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",93981,MCI Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",93982,"MCI Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",93983,"MCI Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",93988,MCI Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",93989,MCI Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94461,Thomas Built Van Based,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94981,Thomas Built Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94982,"Thomas Built Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94983,"Thomas Built Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94988,Thomas Built Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94989,Thomas Built Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",94999,Thomas Built Unknown(THOMAS BUILT),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",97997,Not Reported Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98301,Other Make Think,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98302,Other Make Meyers Motor,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98398,Other Make Other (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98498,Other Make Other (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98598,Other Make Other (LSV/NEV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98701,Other Make 0-50cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98702,Other Make 51-124cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98703,Other Make 125-349cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98704,Other Make 350-449cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98705,Other Make 450-749cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98706,Other Make 750cc or greater,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98707,Other Make Electric Motorcycle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98709,Other Make Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98731,Other Make 0-50cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98732,Other Make 51-124cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98733,Other Make 125-349cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98734,Other Make 350cc or greater (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98739,Other Make Unknown cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98802,Other Make Auto-Union-DKW,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98803,Other Make Divco,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98804,Other Make Western Star,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98805,Other Make Oshkosh,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98806,Other Make Hino,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98807,Other Make Scania,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98808,Other Make UD,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98809,Other Make Sterling,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98850,Other Make Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98870,Other Make Medium/Heavy Van-Based Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98881,Other Make Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98882,Other Make Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98883,Other Make Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98884,Other Make Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98890,Other Make Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98898,Other Make Other (medium/heavy truck)**,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98902,Other Make Neoplan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98903,Other Make Carpenter,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98904,Other Make Collins Bus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98905,Other Make DINA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98906,Other Make Mid Bus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98907,Other Make Orion,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98908,Other Make Van Hool,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98981,Other Make Bus***: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98982,"Other Make Bus: Front engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98983,"Other Make Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98988,Other Make Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98998,Other Make Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",98999,Other Make Unknown (OTHER MAKE),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99399,Unknown Make Unknown (automobile),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99499,Unknown Make Unknown (light truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99598,Unknown Make Unknown (LSG/NGV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99599,Unknown Make Unknown (LSV/NGV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99701,Unknown Make 0-50cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99702,Unknown Make 51-124cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99703,Unknown Make 125-349cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99704,Unknown Make 350-449cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99705,Unknown Make 450-749cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99706,Unknown Make 750cc or greater,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99707,Unknown Make Electric Motorcycle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99709,Unknown Make Unknown cc,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99731,Unknown Make 0-50cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99732,Unknown Make 51-124cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99733,Unknown Make 125-349cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99734,Unknown Make 350cc or greater (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99739,Unknown Make Unknown cc (ATV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99850,Unknown Make Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99870,Unknown Make Medium Heavy Van-Based Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99881,Unknown Make Medium/Heavy - CBE,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99882,Unknown Make Medium/Heavy - COE low entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99883,Unknown Make Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99884,Unknown Make Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99890,Unknown Make Medium/Heavy - COE entry position unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99898,Unknown Make Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99981,Unknown Make Bus**: Conventional (Engine out front),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99982,Unknown Make Bus: Front engine. Flat front,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99983,"Unknown Make Bus: Rear engine, Flat front",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99988,Unknown Make Other (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99989,Unknown Make Unknown (bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99998,Unknown Make Other (vehicle),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",99999,"Unknown Make Unknown (as to automobile, motored cycle, light truck or truck)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",1,"Convertible(excludes sun-roof,t-bar)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",2,"2-door sedan,hardtop,coupe",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",3,3-door/2-door hatchback,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",4,"4-door sedan, hardtop",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",5,5-door/4-door hatchback,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",6,Station Wagon (excluding van and truck based),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",7,"Hatchback, number of doors unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",8,"Sedan/Hardtop, number of doors unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",9,Other or Unknown automobile type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",10,"Auto-based pickup (includes E1 Camino, Caballero, Ranchero, SSR, G8-ST, Subaru Brat, Rabbit Pickup)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",11,"Auto-based panel (cargo station wagon, auto-based ambulance or hearse)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",12,Large Limousine-more than four side doors or stretched chassis,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",13,Three-wheel automobile or automobile derivative,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",14,"Compact Utility (Utility Vehicle Categories ""Small"" and ""Midsize"")",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",15,"Large utility (ANSI D16.1 Utility Vehicle Categories and ""Full Size"" and ""Large"")",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",16,"Utility station wagon (includes suburban limousines, Suburban, Travellall, Grand Wagoneer)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",17,3-door coupe,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",19,"Utility Vehicle, Unknown body type",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",20,"Minivan (Chrysler Town and Country, Caravan, Grand Caravan, Voyager, Voyager, Honda-Odyssey, ...)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",21,"Large Van-Includes van-based buses (B150-B350, Sportsman, Royal Maxiwagon, Ram, Tradesman,...)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",22,"Step-van or walk-in van (GVWR less than or equal to 10,000 lbs.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",28,"Other van type (Hi-Cube Van, Kary)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",29,Unknown van type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",33,Convertible pickup,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",34,Light Pickup,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",39,Unknown (pickup style) light conventional truck type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",40,"Cab Chassis Based (includes Rescue Vehicle, Light Stake, Dump, and Tow Truck)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",41,Truck based panel,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",42,Light Vehicle Based Motor Home [chassis mounted],NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",45,Other light conventional truck type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",48,Unknown light truck type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",49,"Unknown light vehicle type (automobile,utility vehicle, van, or light truck)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",50,School Bus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",51,Cross Country/Intercity Bus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",52,Transit Bus (City Bus),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",55,"Van-Based Bus GVWR greater than 10,000 lbs.",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",58,Other Bus Type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",59,Unknown Bus Type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",60,"Step van (GVWR greater than 10,000 lbs.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",61,"Single-unit straight truck or Cab-Chassis (GVWR range 10,001 to 19,500 lbs.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",62,"Single-unit straight truck or Cab-Chassis (GVWR range 19,501 to 26,000 lbs.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",63,"Single-unit straight truck or Cab-Chassis (GVWR greater than 26,000 lbs.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",64,Single-unit straight truck or Cab-Chassis (GVWR unknown),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",65,Medium/Heavy Vehicle Based Motor Home,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",66,"Truck-tractor (Cab only, or with any number of trailing unit; any weight)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",67,"Medium/heavy Pickup (GVWR greater than 10,000 lbs.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",71,"Unknown if single-unit or combination unit Medium Truck (GVWR range 10,001 lbs. to 26,000 lbs.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",72,"Unknown if single-unit or combination unit Heavy Truck (GVWR greater than 26,000 lbs.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",73,"Camper or Motor Home, unknown GVWR",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",78,Unknown medium/heavy truck type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",79,Unknown truck type (light/medium/heavy),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",80,Two Wheel Motorcycle (excluding motor scooters),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",81,Moped or motorized bicycle,NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",82,Three-wheel Motorcycle (2 Rear Wheels),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",83,Off-road Motorcycle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",84,Motor Scooter,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",85,Unenclosed Three Wheel Motorcycle / Unenclosed Autocycle (1 Rear Wheel),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",86,Enclosed Three Wheel Motorcycle / Enclosed Autocycle (1 Rear Wheel),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",87,Unknown Three Wheel Motorcycle Type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",88,"Other motored cycle type (mini-bikes, pocket motorcycles ""pocket bikes"")",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",89,Unknown motored cycle type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",90,ATV/ATC [All-Terrain Cycle],NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",91,Snowmobile,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",92,Farm equipment other than trucks,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",93,Construction equipment other than trucks (includes graders),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",94,Low Speed Vehicle (LSV) / Neighborhood Electric Vehicle (NEV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",95,Golf Cart,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",96,Recreational Off-Highway Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",97,"Other vehicle type (includes go-cart, fork-lift, city street sweeper dunes/swamp buggy)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",98,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",99,Unknown body type,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,MCARR_I2,mcarr_i2,MCID Identification Number,This data element records the motor carrier identification number if applicable to this vehicle.,"The Carrier Identification Number is found only on vehicles of interstate for-hire or private carriers in the transportation business. It is the unique number assigned to the Carrier by the United States Department of Commerce Commission, or the State. The number can be either a U.S. DOT number (on interstate private carriers) or an ICC MC number (interstate for-hire carriers). Collected only for buses and trucks over 4,500 kg GVWR, this data element is applicable to the following vehicles:    •   Medium/Heavy Trucks: vehicles with two axles/six tires and/or gross weight greater than        10,000 pounds.    •   Buses with 16 or more seats (including the driver).    •   Trucks and Vans of any size carrying hazardous cargo.    •    Light commercial trucks pulling a trailer with gross combination weight rating (GCWR)         greater than 10,000 pounds. Prior to 2016 the Data Element ID was V16B. From 2016 to 2019 the Data Element ID was V17B. This data element also appears in the Parkwork data file as PMCARR_I2.",0,Not Applicable,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,10,NA,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,12,NA,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,19,Motor Vehicle Used for Vehicle Sharing Mobility,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,20,Motor Vehicle Used for Electronic Ride-hailing,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TOWED,towed,Vehicle Removal,NA,NA,3,Towed But Not Due to Disabling Damage,NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,vehicle,DR_ZIP,dr_zip,Driver ZIP Code,This data element records the ZIP Code of the driver’s address as listed in the case material.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",99998,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,DR_ZIP,dr_zip,Driver ZIP Code,This data element records the ZIP Code of the driver’s address as listed in the case material.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",99999,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2020,2020,NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2020,2020,NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,17,Crossing over (Passing Through) Junction,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,vehicle,VPICMAKE,vpicmake,vPIC Make,This element identifies the Make (manufacturer brand name) of this vehicle as per NHTSA vPIC submissions.,"Refer to Addition of VIN-Decoded Data for more details. For more information on NHTSA’s Product Information Catalog and Vehicle Listing (vPIC), go to https://vpic.nhtsa.dot.gov/. A complete listing of vPIC Makes can be downloaded using the following URL: https://vpic.nhtsa.dot.gov/api/vehicles/getallmakes?format=csv. The vPIC Make Name (make_name) and vPIC Make ID (make_id) in the listing can be used to download the vPIC Models for a particular vPIC Make. (See vPIC Model for more details.) This data element also appears in the Person data file and in the Parkwork data file as PVPICMAKE.",NA,(Self-evident),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,VPICMODEL,vpicmodel,vPIC Model,"This element identifies the Model of this vehicle using NHTSA’s VIN decoder application, vPIC.","Refer to Addition of VIN-Decoded Data for more details. For more information on NHTSA’s Product Information Catalog and Vehicle Listing (vPIC), go to https://vpic.nhtsa.dot.gov/. A complete listing of vPIC Models for a particular vPIC Make can be downloaded using the following URLs as a guide. The first uses vPIC Make ID (make_id) as a search parameter and the second uses vPIC Make Name (make_name). (See vPIC Make for obtaining vPIC Make Names and IDs.)    •   Replace * in the URL with vPIC Make ID:        https://vpic.nhtsa.dot.gov/api/vehicles/GetModelsForMakeId/*?format=csv    •   Replace * in the URL with vPIC Make Name:        https://vpic.nhtsa.dot.gov/api/vehicles/getmodelsformake/*?format=csv Example 1: Use the following URLs to download all the Models for Buick.        Use Buick Make ID 468 as parameter:        https://vpic.nhtsa.dot.gov/api/vehicles/GetModelsForMakeId/468?format=csv        Use the Make Name “Buick” as parameter:        https://vpic.nhtsa.dot.gov/api/vehicles/getmodelsformake/Buick?format=csv Example 2: Use the following URLs to download all the Models for Toyota.        Use Toyota Make ID 448 as parameter:        https://vpic.nhtsa.dot.gov/api/vehicles/GetModelsForMakeId/448?format=csv        Use the Make Name “Toyota” as parameter:        https://vpic.nhtsa.dot.gov/api/vehicles/getmodelsformake/Toyota?format=csv This data element also appears in the Person data file and in the Parkwork data file as PVPICMODEL.",NA,(Self-evident),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,VPICBODYCLASS,vpicbodyclass,vPIC Body Class,"This element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc., as defined by the manufacturer.","Refer to Addition of VIN-Decoded Data for more details. For more information on NHTSA’s Product Information Catalog and Vehicle Listing (vPIC), go to https://vpic.nhtsa.dot.gov/. Attributes with an asterisk (*) must have a finished body class for an incomplete vehicle captured under Final Stage Body Class. Other attributes may have a Final Stage Body Class if VIN decoding indicates that the vehicle is manufactured as an incomplete vehicle. This data element also appears in the Person data file and in the Parkwork data file as PVPICBODYCLASS.",NA,(Self-evident),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",0,Not Applicable,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",108,Motorhome,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",11,Truck,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",111,Step Van / Walk-in Van,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",117,Limousine,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",118,Extended Wagon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",119,Sport Utility Truck,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",15,Wagon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",16,Bus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",2,Minivan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",4,Low Speed Vehicle (LSV),NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",60,Pickup,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",66,Truck - Tractor,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",68,Streetcar / Trolley,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",7,Sport Utility Vehicle (SUV)/Multi Purpose Vehicle (MPV),NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",73,Bus-School Bus,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",8,Crossover Utility Vehicle (CUV),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",9,Van,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",95,Cargo Van,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",997,Other (Specify:),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",998,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",999,Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_FROM,gvwr_from,Power Unit Gross Vehicle Weight Rating From,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,11,"Class 1: 6,000 lbs. or less (2,722 kg or less)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_FROM,gvwr_from,Power Unit Gross Vehicle Weight Rating From,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,12,"Class 2: 6,001 - 10,000 lbs. (2,722 - 4,536 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_FROM,gvwr_from,Power Unit Gross Vehicle Weight Rating From,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,13,"Class 3: 10,001 - 14,000 lbs. (4,536 - 6,350 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_FROM,gvwr_from,Power Unit Gross Vehicle Weight Rating From,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,14,"Class 4: 14,001 - 16,000 lbs. (6,350 - 7,258 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_FROM,gvwr_from,Power Unit Gross Vehicle Weight Rating From,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,15,"Class 5: 16,001 - 19,500 lbs. (7,258 - 8,845 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_FROM,gvwr_from,Power Unit Gross Vehicle Weight Rating From,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,16,"Class 6: 19,501 - 26,000 lbs. (8,845 - 11,794 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_FROM,gvwr_from,Power Unit Gross Vehicle Weight Rating From,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,17,"Class 7: 26,001 - 33,000 lbs. (11,794 - 14,969 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_FROM,gvwr_from,Power Unit Gross Vehicle Weight Rating From,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,18,"Class 8: 33,001 lbs. and above (14,969 kg and above)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_FROM,gvwr_from,Power Unit Gross Vehicle Weight Rating From,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,98,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_FROM,gvwr_from,Power Unit Gross Vehicle Weight Rating From,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,99,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_TO,gvwr_to,Power Unit Gross Vehicle Weight Rating To,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,11,"Class 1: 6,000 lbs. or less (2,722 kg or less)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_TO,gvwr_to,Power Unit Gross Vehicle Weight Rating To,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,12,"Class 2: 6,001 - 10,000 lbs. (2,722 - 4,536 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_TO,gvwr_to,Power Unit Gross Vehicle Weight Rating To,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,13,"Class 3: 10,001 - 14,000 lbs. (4,536 - 6,350 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_TO,gvwr_to,Power Unit Gross Vehicle Weight Rating To,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,14,"Class 4: 14,001 - 16,000 lbs. (6,350 - 7,258 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_TO,gvwr_to,Power Unit Gross Vehicle Weight Rating To,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,15,"Class 5: 16,001 - 19,500 lbs. (7,258 - 8,845 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_TO,gvwr_to,Power Unit Gross Vehicle Weight Rating To,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,16,"Class 6: 19,501 - 26,000 lbs. (8,845 - 11,794 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_TO,gvwr_to,Power Unit Gross Vehicle Weight Rating To,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,17,"Class 7: 26,001 - 33,000 lbs. (11,794 - 14,969 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_TO,gvwr_to,Power Unit Gross Vehicle Weight Rating To,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,18,"Class 8: 33,001 lbs. and above (14,969 kg and above)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_TO,gvwr_to,Power Unit Gross Vehicle Weight Rating To,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,98,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,GVWR_TO,gvwr_to,Power Unit Gross Vehicle Weight Rating To,This element identifies the range of gross vehicle weight rating of the power unit as identified by the manufacturer through the vehicle’s VIN submission. GVWR_FROM defines the lowest value and GVWR_TO defines the highest value for the range of the GVWR specified by the manufacturer as the recommended loaded weight for a vehicle.,Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Person data file and in Parkwork data file as PGVWR_FROM and PGVWR_TO.,99,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR1GVWR,trlr1gvwr,Trailer Gross Vehicle Weight Rating (1),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",0,No Trailer GVWR Required,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR1GVWR,trlr1gvwr,Trailer Gross Vehicle Weight Rating (1),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",11,"Class 1: 6,000 lbs or less (2,722 kg or less)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR1GVWR,trlr1gvwr,Trailer Gross Vehicle Weight Rating (1),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",12,"Class 2: 6,001 - 10,000 lbs (2,722 - 4,536 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR1GVWR,trlr1gvwr,Trailer Gross Vehicle Weight Rating (1),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",13,"Class 3: 10,001 - 14,000 lbs (4,536 - 6,350 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR1GVWR,trlr1gvwr,Trailer Gross Vehicle Weight Rating (1),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",14,"Class 4: 14,001 - 16,000 lbs (6,350 - 7,258 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR1GVWR,trlr1gvwr,Trailer Gross Vehicle Weight Rating (1),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",15,"Class 5: 16,001 - 19,500 lbs (7,258 - 8,845 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR1GVWR,trlr1gvwr,Trailer Gross Vehicle Weight Rating (1),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",16,"Class 6: 19,501 - 26,000 lbs (8,845 - 11,794 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR1GVWR,trlr1gvwr,Trailer Gross Vehicle Weight Rating (1),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",17,"Class 7: 26,001 - 33,000 lbs (11,794 - 14,969 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR1GVWR,trlr1gvwr,Trailer Gross Vehicle Weight Rating (1),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",18,"Class 8: 33,001 lbs and above (14,969 kg and above)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR1GVWR,trlr1gvwr,Trailer Gross Vehicle Weight Rating (1),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",77,No Trailing Units,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR1GVWR,trlr1gvwr,Trailer Gross Vehicle Weight Rating (1),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",98,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR1GVWR,trlr1gvwr,Trailer Gross Vehicle Weight Rating (1),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",99,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR2GVWR,trlr2gvwr,Trailer Gross Vehicle Weight Rating (2),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",0,No Trailer GVWR Required,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR2GVWR,trlr2gvwr,Trailer Gross Vehicle Weight Rating (2),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",11,"Class 1: 6,000 lbs or less (2,722 kg or less)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR2GVWR,trlr2gvwr,Trailer Gross Vehicle Weight Rating (2),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",12,"Class 2: 6,001 - 10,000 lbs (2,722 - 4,536 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR2GVWR,trlr2gvwr,Trailer Gross Vehicle Weight Rating (2),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",13,"Class 3: 10,001 - 14,000 lbs (4,536 - 6,350 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR2GVWR,trlr2gvwr,Trailer Gross Vehicle Weight Rating (2),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",14,"Class 4: 14,001 - 16,000 lbs (6,350 - 7,258 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR2GVWR,trlr2gvwr,Trailer Gross Vehicle Weight Rating (2),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",15,"Class 5: 16,001 - 19,500 lbs (7,258 - 8,845 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR2GVWR,trlr2gvwr,Trailer Gross Vehicle Weight Rating (2),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",16,"Class 6: 19,501 - 26,000 lbs (8,845 - 11,794 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR2GVWR,trlr2gvwr,Trailer Gross Vehicle Weight Rating (2),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",17,"Class 7: 26,001 - 33,000 lbs (11,794 - 14,969 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR2GVWR,trlr2gvwr,Trailer Gross Vehicle Weight Rating (2),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",18,"Class 8: 33,001 lbs and above (14,969 kg and above)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR2GVWR,trlr2gvwr,Trailer Gross Vehicle Weight Rating (2),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",77,No Trailing Units,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR2GVWR,trlr2gvwr,Trailer Gross Vehicle Weight Rating (2),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",98,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR2GVWR,trlr2gvwr,Trailer Gross Vehicle Weight Rating (2),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",99,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR3GVWR,trlr3gvwr,Trailer Gross Vehicle Weight Rating (3),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",0,No Trailer GVWR Required,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR3GVWR,trlr3gvwr,Trailer Gross Vehicle Weight Rating (3),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",11,"Class 1: 6,000 lbs or less (2,722 kg or less)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR3GVWR,trlr3gvwr,Trailer Gross Vehicle Weight Rating (3),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",12,"Class 2: 6,001 - 10,000 lbs (2,722 - 4,536 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR3GVWR,trlr3gvwr,Trailer Gross Vehicle Weight Rating (3),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",13,"Class 3: 10,001 - 14,000 lbs (4,536 - 6,350 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR3GVWR,trlr3gvwr,Trailer Gross Vehicle Weight Rating (3),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",14,"Class 4: 14,001 - 16,000 lbs (6,350 - 7,258 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR3GVWR,trlr3gvwr,Trailer Gross Vehicle Weight Rating (3),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",15,"Class 5: 16,001 - 19,500 lbs (7,258 - 8,845 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR3GVWR,trlr3gvwr,Trailer Gross Vehicle Weight Rating (3),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",16,"Class 6: 19,501 - 26,000 lbs (8,845 - 11,794 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR3GVWR,trlr3gvwr,Trailer Gross Vehicle Weight Rating (3),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",17,"Class 7: 26,001 - 33,000 lbs (11,794 - 14,969 kg)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR3GVWR,trlr3gvwr,Trailer Gross Vehicle Weight Rating (3),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",18,"Class 8: 33,001 lbs and above (14,969 kg and above)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR3GVWR,trlr3gvwr,Trailer Gross Vehicle Weight Rating (3),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",77,No Trailing Units,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR3GVWR,trlr3gvwr,Trailer Gross Vehicle Weight Rating (3),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",98,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehicle,TRLR3GVWR,trlr3gvwr,Trailer Gross Vehicle Weight Rating (3),This element identifies the gross vehicle weight rating of any trailing units as identified by the manufacturer in the vehicle’s VIN.,"Refer to Addition of VIN-Decoded Data for more details. These data elements also appear in the Parkwork data file as PTRLR1GVWR, PTRLR2GVWR, and PTRLR3GVWR.",99,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,11,Person on Motorized Personal Conveyance,NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,12,Person on Non-Motorized Personal Conveyance,NA,NA,NA,NA,NA,NA,1,1,1,NA
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,13,"Person on Personal Conveyance, Unknown if Motorized or Non-Motorized",NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,person,HOSPITAL,hospital,Transported to First Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",0,Not Transported for Treatment,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,HOSPITAL,hospital,Transported to First Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",1,EMS Air,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,HOSPITAL,hospital,Transported to First Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",2,Law Enforcement,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,HOSPITAL,hospital,Transported to First Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",3,EMS Unknown Mode,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,HOSPITAL,hospital,Transported to First Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",4,Transported  Unknown Source,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,HOSPITAL,hospital,Transported to First Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",5,EMS Ground,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,HOSPITAL,hospital,Transported to First Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",6,Other,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,HOSPITAL,hospital,Transported to First Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",8,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,HOSPITAL,hospital,Transported to First Medical Facility By,This data element identifies the mode of transportation to a hospital or medical facility provided for this person.,"Prior to 2008 this data element’s name was “Taken to Hospital or Treatment Facility.” From 2008 to 2009 this data element was called “Transported for Treatment By.” From 2010 to 2012 this data element’s name was “Transported to Medical Facility By.” Prior to 2019 the Data Element ID was P22/NM21. From 2019-2021 the Data Element ID was P22/NM22. This field exists in the 1975 and 1976 data file, but is not initialized, i.e., it has no values.",9,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,DEATH_DA,death_da,Death Date (Day),This data element records the day of the month of this person’s death.,"Prior to 2019 the Data Element ID was P24B/NM23B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24B/NM24B.",97,Redacted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,DEATH_MO,death_mo,Death Date (Month),This data element records the month of this person’s death.,"Prior to 2019 the Data Element ID was P24A/NM23A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24A/NM24A.",97,Redacted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2021,2021,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",9997,Redacted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,DEATH_HR,death_hr,Death Time (Hour),This data element records the hour of this person’s death utilizing the 24-hour clock format.,"Prior to 2019 the Data Element ID was P25A/NM24A. From 2019-2021 the Data Element ID was P25A/NM25A. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",97,Redacted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,DEATH_MN,death_mn,Death Time (Minutes),This data element records the minutes after the hour of this person’s death.,"Prior to 2019 the Data Element ID was P25B/NM24B. From 2019-2021 the Data Element ID was P25B/NM25B. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",97,Redacted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,DEATH_TM,death_tm,Death Time,This data element records the hour and minute of this person’s death utilizing the 24-hour clock format.,"Four digits; DEATH_HR followed by DEATH_MN, e.g., Valid Military Times 0643 for 6:43 a.m. Prior to 2019 the Data Element ID was P25/NM24. From 2019-2021 the Data Element ID was P25/NM25. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",9797,Redacted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,WORK_INJ,work_inj,Fatal Injury at Work,"This data element records whether the death certificate indicated this person was ""at work"" at the time of the crash.","In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",7,Redacted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,person,HISPANIC,hispanic,Hispanic Origin,This data element records the Hispanic origin of this person from the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",97,Redacted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",1,Clear,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",2,Rain,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",3,Sleet or Hail,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",4,Snow,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",5,"Fog, Smog, Smoke",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",6,Severe Crosswinds,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",7,"Blowing Sand, Soil, Dirt",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",8,Other,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",10,Cloudy,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",11,Blowing Snow,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",12,Freezing Rain or Drizzle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",98,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,weather,WEATHER,weather,Atmospheric Condition,This derived data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material. This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.,"Prior to 2007 one value was coded for atmospheric condition. From 2007-2019 this data element was derived from up to two conditions that could be selected, WEATHER1 and WEATHER2, based on a hierarchy. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file, and this data element is derived from those multiple responses using the same hierarchy. See Appendix B: Rules for Derived Data Elements for an explanation of how this data element is derived. Prior to 2015 the Data Element ID was C25. Prior to 2007 one value was coded for atmospheric conditions. From 2007-2019 up to two values could be selected. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019. Beginning in 2020 all applicable atmospheric conditions are selected and stored in the Weather data file. Only the derived data element WEATHER is still stored in the Accident data file. It is now derived from the multiple responses in the Weather data file using the same hierarchy. Prior to 2015 the Data Element ID was C25. Prior to 2020 this data element identified up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 were the coded data elements, and Accident.WEATHER was derived from these two. The two coded data elements were discontinued after 2019 and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Beginning in 2020 all applicable atmospheric conditions are selected and stored in this data file. Only the derived data element WEATHER is still stored in the Accident data file and is now derived from the responses in this data file using the same hierarchy.",99,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",0,None,NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",1,"Inadequate Warning of Exits, Lanes Narrowing, Traffic Controls, etc.",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",2,Shoulder Design or Condition,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",3,Other Maintenance or Construction-Created Condition,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",4,No or Obscured Pavement Marking,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",5,Surface Under Water,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",6,"Inadequate Construction or Poor Design of Roadway,Bridge, etc.",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",7,"Surface Washed Out(caved-in, road slippage)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",12,Distracted Driver of a Non-Contact Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",13,Aggressive Driving / Road Rage by Non-contact Vehicle Driver,NA,NA,NA,NA,NA,NA,1,1,1,NA
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",14,"Motor Vehicle struck by falling cargo,or something that came loose from or something that was set in motion by a vehicle",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",15,"Non-occupant struck by falling cargo, or something that came loose from, or something that was set in motion by a vehicle",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",16,Non-occupant struck vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",17,Vehicle set-in-motion by non-driver,NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",18,Date of Crash and Date of EMS Notification were not the same day,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",19,Recent/Previous Crash scene Nearby,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",20,Police Pursuit Involved,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",21,Within Designated School Zone,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",22,Speed Limit is a Statutory Limit as Recorded or was determined as this state`s `basic rule`,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",23,Indication of a Stalled/Disabled Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",24,Unstabilized Situation Began and All Harmful Events Occurred Off of the Roadway,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",25,Toll Booth/Plaza Related,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",26,Prior Non-Recurring Incident,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",27,Backup Due to Prior Crash,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",28,Regular Congestion,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",30,Obstructed Crosswalks,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",31,Related to a Bus Stop,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",999,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",0,Not Distracted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",3,By Other Occupant(s),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",4,By a Moving Object in Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",5,While Talking or Listening to Mobile Phone,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",6,While Manipulating Mobile Phone,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",7,Adjusting Audio Or Climate Controls,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",9,While Using Other Component/Controls Integral to Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",10,While Using or Reaching for Device/Object Brought into Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",12,"Distracted by Outside Person, Object or Event",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",13,Eating or Drinking,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",14,Smoking Related,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",15,Other Mobile Phone Related,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",16,No Driver Present/Unknown if Driver present,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",17,Distraction/Inattention,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",18,Distraction/Careless,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",19,Careless/Inattentive,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",92,"Distraction (Distracted), Details Unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",93,"Inattention (Inattentive), Details Unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",96,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",97,Lost in Thought / Day dreaming,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",98,Other Distraction [Specify:],NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,distract,DRDISTRACT,drdistract,Driver Distracted By,This data element identifies the attributes that best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction from the primary task of driving occurs when drivers divert their attention from the driving task to some other activity. Also, driving while daydreaming or lost in thought is identified as distracted driving by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Although the attribute 1 (Looked but Did Not See) was included in this element, this attribute is not considered a distraction and therefore should not be included in any distraction analysis.",99,Reported as Unknown if Distracted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",8,"Emotional (depressed, angry, disturbed, etc.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",0,None Noted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",1,Tires,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",2,Brake System,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",3,Steering,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",4,Suspension,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",5,Power Train,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",6,Exhaust System,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",7,Head Lights,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",8,Signal Lights,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",9,Other Lights,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",10,Wipers,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",11,Wheels,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",12,Mirrors,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",13,Windows/Windshield,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",14,"Body, Doors",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",15,Truck Coupling/Trailer Hitch/Safety Chains,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",16,Safety Systems,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",17,Vehicle Contributing Factors - No Details,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",97,Other,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,factor,VEHICLECC,vehiclecc,"Contributing Circumstances, Motor Vehicle",This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.,"Most of these data elements can be found in Related Factor—Vehicle Level (SAS names VEH_CF1 and VEH_CF2 in the Vehicle data file in 2009 and prior, and VEH_SC1-VEH_SC2 in 2010).",99,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,maneuver,MANEUVER,maneuver,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,0,Driver Did Not Maneuver to Avoid,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,maneuver,MANEUVER,maneuver,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,1,Object,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,maneuver,MANEUVER,maneuver,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,2,"Poor Road Conditions (Puddle, Ice, Pothole, etc.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,maneuver,MANEUVER,maneuver,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,3,Live Animal,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,maneuver,MANEUVER,maneuver,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,4,Contact Motor Vehicle (In this crash),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,maneuver,MANEUVER,maneuver,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,5,"Pedestrian, Pedalcyclist or Other Non-Motorist",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,maneuver,MANEUVER,maneuver,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,92,Phantom/Non-Contact Motor Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,maneuver,MANEUVER,maneuver,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,95,No Driver Present/Unknown if Driver present,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,maneuver,MANEUVER,maneuver,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,98,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,maneuver,MANEUVER,maneuver,Driver Maneuvered To Avoid,"This data element identifies the things this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.",NA,99,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,0,None,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,1,Manslaughter or homicide,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,2,Willful reckless driving; driving to endanger; negligent driving,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,3,"Unsafe reckless (not willful, wanton reckless) driving",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,4,"Inattentive, careless, improper driving, driving without due care",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,5,Fleeing or eluding police,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,6,"Fail to obey police, fireman, authorized person directing traffic",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,7,"Hit-and-run, fail to stop after crash",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,8,"Fail to give aid, info., wait for police after crash",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,9,Serious violation resulting in death,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,10,Use of Telecommunications Device,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,11,Driving while intoxicated (alcohol or drugs) or BAC above limit (any detectable BAC for CDLs),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,12,Driving while impaired,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,13,Driving under influence of substance not intended to intoxicate,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,14,Drinking while operating,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,15,Illegal possession of alcohol or drugs,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,16,Driving with detectable alcohol,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,18,Refusal to submit to chemical test,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,19,"Alcohol, drug, or impairment violations generally",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,21,Racing,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,22,Speeding (above the speed limit),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,23,Speed greater than reasonable & prudent (not necessarily over the limit),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,24,"Exceeding special speed limit (e.g. for trucks, buses, cycles, or on bridge, in school zone, etc.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,25,"Energy speed (exceeding 55 mph, non-pointable)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,26,Driving too slowly,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,29,"Speed related violations, generally",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,31,Fail to stop for red signal,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,32,Fail to stop for flashing red,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,33,"Violation of turn on red (fail to stop & yield, yield to pedestrians before turning)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,34,Fail to obey flashing signal (yellow or red),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,35,Fail to obey signal generally,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,36,Violate RR grade crossing device/regulations,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,37,Fail to obey stop sign,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,38,Fail to obey yield sign,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,39,Fail to obey traffic control device,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,41,"Turn in violation of traffic control (disobey signs, turn arrow or pavement markings; not a right on red violation)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,42,"Improper method & position of turn (too wide, wrong lane)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,43,Fail to signal for turn or stop,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,45,Fail to yield to emergency vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,46,Fail to yield generally,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,48,Enter intersection when space insufficient,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,49,"Turn, yield, signaling violations generally",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,51,Driving wrong way on one-way road,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,52,"Driving on left, wrong side of road, generally",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,53,"Improper, unsafe passing",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,54,Pass on right (drive off pavement to pass),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,55,Pass stopped school bus,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,56,Fail to give way when overtaken,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,58,Following too closely,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,59,"Wrong side, passing, following violations, generally",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,61,Unsafe or prohibited lane change,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,62,"Improper use of lane (enter of 3-lane road, HOV designated lane)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,63,"Certain traffic to use right lane (trucks, slow moving, etc.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,66,"Motorcycle lane violations (more than two per lane, riding between lanes, etc.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,67,Motorcyclist attached to another vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,69,"Lane violations, generally",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,71,Driving while license withdrawn,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,72,Other driver license violations,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,73,"Commercial driver violations (log book, hours, permits carried)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,74,Vehicle registration violations,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,75,Fail to carry insurance card,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,76,Driving uninsured vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,79,Non-moving violations generally,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,81,Lamp violations,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,82,Brake violations,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,83,Failure to require restraint use (by self or passengers),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,84,"Motorcycle equipment violations (helmet, special equipment)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,85,Violation of hazardous cargo regulations,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,86,"Size, weight, load violations",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,89,Equipment violations generally,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,91,Parking,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,92,"Theft, unauthorized use of motor vehicle",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,93,"Driving where prohibited (sidewalk, limited access, off truck route)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,95,No Driver Present/Unknown if Driver Present,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,97,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,98,"Other moving violation (coasting, backing, opening door)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,violatn,VIOLATION,violation,Violations Charged,"This data element documents the violations, citations, or infractions of the Vehicle Code issued on the police crash report for this driver in this crash, regardless of whether the driver survived the crash.",Prior to 2010 this data element was in the Vehicle data file. In 2010 this data element changed to identify all violations charged in the crash and was therefore moved here to its own data file.,99,Unknown Violation(s),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,0,No Obstruction Noted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,1,"Rain, Snow, Fog, Smoke, Sand, Dust",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,2,"Reflected Glare, Bright Sunlight, Headlights",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,3,"Curve, Hill or Other Roadway Design Feature",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,4,"Building, Billboard, Other Structure",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,5,"Trees, Crops, Vegetation",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,6,In-Transport Motor Vehicle (including load),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,7,"Not In-Transport Motor Vehicle (parked, working)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,8,Splash or Spray of Passing Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,9,Inadequate Defrost or Defog System,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,10,Inadequate Vehicle Lighting System,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,11,Obstruction Interior to the Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,12,External Mirrors,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,13,Broken or Improperly Cleaned Windshield,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,14,Obstructing Angles on Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,95,No Driver Present/Unknown if Driver present,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,97,Vision Obscured - No Details,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,98,Other Visual Obstruction,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vision,VISION,vision,Driver(s) Vision Obscured By,This data element records impediments to this driver’s visual field that were noted in the case materials.,Most of these data elements can be found in “Related Factor – Driver Level” from 1982 to 2008. This data element was added to the Vehicle data file in 2009. In 2010 the data element was changed to identify all that apply in the crash and was therefore moved here to its own data file.,99,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,1,1 Clock Value,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,2,2 Clock Value,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,3,3 Clock Value,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,4,4 Clock Value,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,5,5 Clock Value,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,6,6 Clock Value,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,7,7 Clock Value,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,8,8 Clock Value,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,9,9 Clock Value,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,10,10 Clock Value,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,11,11 Clock Value,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,12,12 Clock Value,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,13,Top,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,14,Undercarriage,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,15,No Damage,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,damage,DAMAGE,damage,Areas of Impact - Damaged Areas,This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case material.,Prior to 2016 the Data Element ID was V28B. From 2016 to 2019 the Data Element ID was V29B.,99,Damage Areas Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",NA,(Self-evident),NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",NA,(Self-evident),NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",0,None,NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",4,Reaction to or Failure to Take Drugs/Medication,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",6,"Careless Driving, Inattentive Operation, Improper Driving, Driving Without Due Care",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",8,Aggressive Driving / Road Rage,NA,NA,NA,NA,NA,NA,1,1,1,NA
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",10,Looked But Did Not See,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",12,Mother of Dead Fetus/ Mother of Infant Born Post Crash,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",13,Mentally Challenged,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",15,"Seat Back Not In Normal Upright Position, Seat Back Reclined",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",16,Police or Law Enforcement Officer,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",18,Traveling on Prohibited Trafficways,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",19,Legally Driving on Suspended or Revoked License,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",20,Leaving Vehicle Unattended with Engine Running. Leaving Vehicle Unattended in Roadway,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",21,Overloading or Improper Loading of Vehicle with Passengers or Cargo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",22,Towing or Pushing Vehicle Improperly,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",23,Failing to Dim Lights or to Have Lights on When Required,NA,NA,NA,NA,NA,NA,1,NA,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",24,Operating without Required Equipment,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",26,Following Improperly,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",27,Improper or Erratic Lane Changing,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",28,Improper Lane Usage,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",29,Intentional Illegal Driving Off the Roadway,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",30,Making Improper Entry to or Exit from Trafficway,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",31,Starting or Backing Improperly,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",32,Opening Closure into Moving Traffic or While Vehicle is in Motion,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",33,"Passing where Prohibited by Posted Signs, Pavement Markings or School Bus Displaying Warning not to Pass",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",34,Improper Passing Location,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",35,Passing with Insufficient Distance or Inadequate Visibility or Failing to Yield to Overtaking Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",36,"Operating the Vehicle in an Erratic, Reckless or Negligent Manner.",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",37,Police Pursuing this Driver or Police Officer in Pursuit,NA,NA,NA,NA,NA,NA,1,1,1,NA
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",38,Failure to Yield Right-of-Way,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",39,"Failure to Obey Actual Traffic Signs, Traffic Control Devices, or Traffic Officers. Failure to Obey Safety Zone Traffic Laws",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",40,Passing Through or Around Barrier,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",41,Failure to Observe Warnings or Instructions on Vehicles Displaying Them,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",42,Failure to Signal Intentions,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",45,Driving Less than Posted Minimum,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",47,Making Right Turn From Left-Turn Lane. Make Left Turn From Right-Turn Lane,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",48,Making Other Improper Turn,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",50,Driving Wrong Way on One-Way Trafficway,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",51,Driving on Wrong Side of Two-Way Trafficway (Intentional or Unintentional),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",52,Operator Inexperience,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",53,Unfamiliar with Roadway,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",54,Stopped in Roadway (Vehicle Not Abandoned),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",55,Improper Management of Vehicle Controls (Specify:),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",56,Object Interference with Vehicle Controls (Specify:),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",57,Driving with Tire-Related Problems,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",58,Overcorrecting,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",59,Getting Off/Out of a Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",60,Alcohol and/or Drug Test Refused,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",73,Driver has not complied with Learner`s Permit or Intermediate Driver License Restrictions (GDL Restrictions),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",74,Driver Has Not Complied With Physical or Other Imposed Restrictions (not including GDL Restrictions),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",77,Severe Crosswind,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",78,Wind from Passing Truck,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",79,Slippery or Loose Surface,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",80,Tire Blowout or Flat,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",81,Debris or Objects in Road,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",82,"Ruts, Holes, Bumps in Road",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",83,Live Animals in Road,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",84,Vehicle in Road,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",85,Phantom Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",86,"Pedestrian, Pedal Cyclist or Other Non-Motorist",NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",87,"Ice, Snow, Slush, Water, Sand, Dirt, Oil, Wet Leaves on Road",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",88,Trailer Fishtailing or swaying,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",89,Driver Has a Driving Record or Driver`s License From More Than One State,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",91,"Non-Traffic Violation Charged - manslaughter, homicide or other assault committed without malice.",NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",94,Emergency Medical Service Personnel,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",95,Fire Personnel,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",96,Tow Operator,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",97,"Transportation (i.e. maintenance workers, safety service patrol operators, etc.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",999,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,11,Person on Motorized Personal Conveyance,NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,12,Person on Non-Motorized Personal Conveyance,NA,NA,NA,NA,NA,NA,1,1,1,NA
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,13,"Person on Personal Conveyance, Unknown if Motorized or Non-Motorized",NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,741,NA,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,742,NA,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'7',Not a Pedestrian,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'8',Not Applicable,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'1a',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'1b',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'1c',"Motorist traveling straight through - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, approach direction unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'1d',"Motorist traveling straight through - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, other",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'2a',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'2b',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'2c',"Motorist traveling straight through - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, approach direction unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'2d',"Motorist traveling straight through - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, other",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'3a',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'3b',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'3c',"Motorist traveling straight through - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, approach direction unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'3d',"Motorist traveling straight through - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, other",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'4a',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'4b',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'4c',"Motorist traveling straight through - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, approach direction unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'4d',"Motorist traveling straight through - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, other",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'5a',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'5b',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'5c',"Motorist turning right - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, approach direction unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'5d',"Motorist turning right - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, other",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'6a',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'6b',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'6c',"Motorist turning right - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, approach direction unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'6d',"Motorist turning right - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, other",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'7a',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'7b',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'7c',"Motorist turning right - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, approach direction unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'7d',"Motorist turning right - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, other",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'8a',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'8b',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'8c',"Motorist turning right - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, approach direction unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'8d',"Motorist turning right - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, other",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'9a',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'9b',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'9c',"Motorist turning left - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, approach direction unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'9d',"Motorist turning left - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian within crosswalk area, other",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'10a',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'10b',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'10c',"Motorist turning left - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, approach direction unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'10d',"Motorist turning left - Crash Occurred on Near (Approach) Side of Intersection / Pedestrian outside crosswalk area, other",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'11a',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'11b',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'11c',"Motorist turning left - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, approach direction unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'11d',"Motorist turning left - Crash Occurred on Far Side of Intersection / Pedestrian within crosswalk area, other",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'12a',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'12b',NA,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'12c',"Motorist turning left - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, approach direction unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'12d',"Motorist turning left - Crash Occurred on Far Side of Intersection / Pedestrian outside crosswalk area, other",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDSNR,pedsnr,Pedestrian Scenario,This data element identifies the location and travel directions of the motorist and pedestrian for those crashes that occur at intersections. This data element summarizes the movements of the pedestrian and motorist in an intersection area.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB37.,'99',Unknown/Insufficient Information,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,740,NA,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",0,None Noted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",1,Dart-Out - Visual Obstruction Noted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",2,Failure to Yield Right-Of-Way,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",3,"Failure to Obey Traffic Signs, Signals or Officer",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",4,"In Roadway Improperly (Standing, Lying, Working, Playing, etc.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",5,Entering/Exiting Parked or Stopped Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",6,"Inattentive (Talking, Eating, Etc.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",7,Improper Turn/Merge,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",8,Improper Passing,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",9,Wrong-Way Riding or Walking,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",10,Riding on Wrong Side of Road,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",11,"Dash - Run, No Visual Obstruction Noted",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",12,Improper Crossing of Roadway or Intersection (Jaywalking),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",13,Failing to Have Lights on When Required,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",14,Operating Without Required Equipment,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",15,Improper or Erratic Lane Changing,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",16,Failure to Keep in Proper Lane or Running Off Road,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",17,Making Improper Entry to or Exit From Trafficway,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",18,"Operating in other Erratic, Reckless, Careless or Negligent Manner",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",19,"Not Visible (Dark clothing, No Lighting, etc.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",20,Passing with Insufficient Distance or Inadequate Visibility or Failing to Yield to Overtaking Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",21,Other (Specify:),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",99,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",8,"Emotional (depressed, angry, disturbed, etc.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",1,Going To or From School (K-12),NA,NA,NA,NA,NA,NA,1,1,1,NA
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",2,Waiting to Cross Roadway,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",3,Crossing Roadway,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",4,Jogging/Running,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",5,Movement Along Roadway with Traffic (In or Adjacent to Travel Lane),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",6,Movement Along Roadway Against Traffic (In or Adjacent to Travel Lane),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",8,"In Roadway - Other (Working, Playing, Etc.)",NA,NA,NA,NA,NA,NA,1,1,1,NA
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",9,"Stationary and Adjacent to Roadway (e.g., Shoulder, Median, Sidewalk)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",10,Working in Trafficway (Incident Response),NA,NA,NA,NA,NA,NA,1,1,1,NA
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",11,Entering / Exiting Parked or Stopped Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",12,"Disabled Vehicle Related (Working on, Pushing, Leaving/Approaching)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",14,Other (Specify:),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",16,Movement Along Roadway - Direction Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",98,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",99,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",0,Not Distracted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",2,By Other Non-Motorist(s),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",3,By a Driver or Occupant of a Motor Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",5,While Talking or Listening to Mobile Phone,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",6,While Manipulating Mobile Phone,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",7,Adjusting or listening to Portable Audio Device (Other than on a Mobile Phone),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",8,"Adjusting, Talking to, or Manipulating Other Portable Electronic Device",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",12,"Distracted by Animal, Other Object, Event, or Activity",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",13,Eating or Drinking,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",14,Smoking Related,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",15,Other Mobile Phone Related,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",17,Distraction/Inattention,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",18,Distraction/Careless,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",19,Careless/Inattentive,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",92,"Distraction (Distracted), Details Unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",93,"Inattention (Inattentive), Details Unknown",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",96,Not Reported,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",97,Lost in Thought/Day Dreaming,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",98,Other Distraction (Specify:),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,nmdistract,NMDISTRACT,nmdistract,Non-Motorist Distracted By,This data element identifies the attributes that best describe this non-motorist’s attention prior to the non-motorist’s involvement in this crash. This element reports on the presence of any distractions that may or may not have contributed to the crash.,"Distraction, for a non-motorist, occurs when a non-motorist’s attention is diverted from the task of navigating in public to some other activity. Also, daydreaming or lost in thought are identified as distractions by NHTSA. Physical conditions/impairments (fatigue, alcohol, medical condition, etc.) or psychological states (anger, emotional, depressed, etc.) are not identified as distractions by NHTSA. Prior to 2022 the Element Data ID was NM13.",99,Reported as Unknown if Distracted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",96,Redacted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",NA,NA,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",NA,Multiple Race - White,NA,NA,NA,NA,NA,NA,1,1,1,NA
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",202,Multiple Race - Black or African American,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",203,Multiple Race - North American Indian or Alaska Native,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",204,Multiple Race - Chinese,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",205,Multiple Race - Japanese,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",206,Multiple Race - Native Hawaiian,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",207,Multiple Race - Filipino,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",218,Multiple Race - Asian Indian,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",219,"Multiple Race - Other Indian (includes South and Central America, any others, except North American or Asian Indians)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",228,Multiple Race - Korean,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",238,Multiple Race - Samoan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",248,Multiple Race - Vietnamese,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",258,Multiple Race - Guamanian or Chamorro,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",268,Multiple Race - Other Asian or Pacific Islander,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",278,"Multiple Race - Asian or Pacific Islander, No Specific (individual) Race",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",298,Multiple Race - Other Races*/,NA,NA,NA,NA,NA,NA,1,1,1,NA
FARS,race,ORDER,order,Order,This data element identifies the order in which the multiple races were listed on the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",97,Redacted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,MULTRACE,multrace,Is Multiple Race?,This data element identifies if multiple races were listed on the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",0,No,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,MULTRACE,multrace,Is Multiple Race?,This data element identifies if multiple races were listed on the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",1,Yes,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,race,MULTRACE,multrace,Is Multiple Race?,This data element identifies if multiple races were listed on the death certificate.,"This data element is only coded for fatalities. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",7,Redacted,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",1,Alabama,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",2,Alaska,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",4,Arizona,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",5,Arkansas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",6,California,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",8,Colorado,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",9,Connecticut,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",10,Delaware,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",11,District of Columbia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",12,Florida,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",13,Georgia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",15,Hawaii,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",16,Idaho,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",17,Illinois,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",18,Indiana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",19,Iowa,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",20,Kansas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",21,Kentucky,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",22,Louisiana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",23,Maine,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",24,Maryland,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",25,Massachusetts,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",26,Michigan,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",27,Minnesota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",28,Mississippi,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",29,Missouri,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",30,Montana,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",31,Nebraska,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",32,Nevada,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",33,New Hampshire,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",34,New Jersey,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",35,New Mexico,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",36,New York,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",37,North Carolina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",38,North Dakota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",39,Ohio,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",40,Oklahoma,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",41,Oregon,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",42,Pennsylvania,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",43,Puerto Rico,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",44,Rhode Island,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",45,South Carolina,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",46,South Dakota,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",47,Tennessee,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",48,Texas,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",49,Utah,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",50,Vermont,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",51,Virginia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",52,Virgin Islands,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",53,Washington,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",54,West Virginia,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",55,Wisconsin,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,STATE,state,State Number,This data element identifies the State in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).,"GSA State data elements except for 43, Puerto Rico. The State in which the vehicle is registered, REG_STAT, is found in the Vehicle data file; the coding is the same.",56,Wyoming,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,VEH_NO,veh_no,Vehicle Number,This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files.,"All vehicles will have a positive integer value. The value 0 is only used for non-motorists (pedestrians, cyclists, etc.) in the Person File. There are no corresponding Vehicle records for non-motorists. ST_CASE and VEH_NO may be used to merge the complete Person File to the Accident File, but including the Vehicle File in the merge will eliminate non-motorists from the merged data. Non-Occupants have VEH_NO = 0, in this case see STR_VEH (N_MOT_NO prior to 2011) under Non-Motorist Striking Vehicle Number in the Person data file.",NA,(Self-evident),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PER_NO,per_no,Person Number,"This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files.","Each occupant of the vehicle is numbered, and each non-occupant is numbered; in the case of a non-occupant the vehicle number is zero. The numbers for occupants are consecutive for each vehicle beginning with 1. Numbers are never skipped. Drivers do not have to be coded 1. Non- Occupants are identified by vehicle number 0 and are numbered consecutively starting with 1 for each non-motorist. To get drivers see data element PER_TYP under Person Type. PER_NO can be used in merges, e.g., when merging the FARS person data file with the multiple cause of death file.",NA,(Self-evident),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",0,None,NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",5,Interfering With Driver,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",8,Mentally Challenged,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",9,Construction/Maintenance/Utility Worker,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",10,Alcohol and/or Drug Test Refused,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",13,Motorized Wheelchair Rider,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",18,Mother of Dead Fetus/Infant Born Post Crash,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",21,Overloading or Improper Loading of Vehicle with Passengers or Cargo,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",26,Following Improperly,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",28,Improper Lane Usage,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",29,"Intentional Illegal Driving on Road Shoulder, in Ditch, on Sidewalk or on Median",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",31,Default Code Used for Vehicle Numbering,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",32,Opening Vehicle Closure into Moving Traffic or While Vehicle is in Motion,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",33,"Passing where Prohibited by Posted Signs, Pavement Markings or School Bus Displaying Warning not to Pass",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",37,Traveling on Prohibited Trafficways,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",40,Passing Through or Around Barrier,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",41,Failure to Observe Warnings or Instructions on Vehicles Displaying Them,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",42,Failure to Signal Intentions,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",44,Driving too Fast for conditions or in Excess of Posted Maximum,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",45,Driving Less than Posted Minimum,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",47,Making Right Turn from Left Turn Lane or Making Left Turn from Right Turn Lane,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",51,Operator Inexperience,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",52,Unfamiliar with Roadway,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",53,Non-Motorist Previously Used a Motor Vehicle for Motion,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",54,Non-Motorist Attempting to Use a Motor Vehicle for Motion,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",55,"Non-Motorist Attempting to Use or Previously Used a Motor Vehicle for Motion, Details Not Reported",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",56,Non-Driver Flees Scene,NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",57,Improper tire Pressure,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",59,Overcorrecting,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",60,"Rain, Snow, Fog, Smoke, Sand, Dust",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",61,"Reflected Glare, Bright Sunlight, Headlights",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",62,"Curve, Hill, or Other Design Features (including traffic signs, embankment)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",63,"Building, Billboard, Other Structures",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",64,"Trees, Crops, Vegetation",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",65,Motor Vehicle (including load),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",66,Parked Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",67,Splash or Spray of Passing Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",68,Inadequate Lighting System,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",69,Obstructing Angles on Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",70,Mirrors,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",72,Other Visual Obstruction,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",73,Severe Crosswind,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",74,Wind From Passing Truck,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",75,Slippery or Loose Surface,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",76,Tire Blow-out or Flat,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",77,Debris or Objects in Road,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",78,"Ruts, Holes, Bump in Road",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",80,Vehicle in Road,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",81,Phantom Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",82,"Pedestrian, Pedal Cyclist or Other Non-Motorist",NA,NA,NA,NA,NA,NA,1,NA,NA,NA
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",83,"Ice, Snow, Slush, Water, Sand, Dirt, Oil, Wet Leaves on Road",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",87,Police or Law Enforcement Officer,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",88,"Seat Back Not in Normal Upright Position, Seat Back Reclined",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",89,Parked Motor Vehicle With Equipment Extending into the Travel Lane,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",90,Non-Motorist Pushing a Vehicle,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",91,Portable Electronic Devices,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",92,Person in Ambulance Treatment Compartment,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",93,Non-Motorist Wearing Motorcycle Helmet,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",94,Emergency Medical Service Personnel,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",95,Fire Personnel,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",96,Tow Operator,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",97,"Transportation (i.e. maintenance workers, safety service patrol operators, etc.)",NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",100,Using a Shared Micromobility Device,NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",101,Obstructed Sidewalk (for this Person),NA,NA,NA,NA,NA,NA,1,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",999,Reported as Unknown,NA,NA,NA,NA,NA,NA,1,1,NA,NA
FARS,vehicle,VIN,vin,Vehicle Identification Number,"This data element records the vehicle identification number (VIN) of this vehicle assigned by the vehicle manufacturer. The VIN contains information on the vehicle such as: manufacturer, model year, model, body type, restraint type, etc.","The vehicle manufacturers use the VIN to describe certain characteristics of a vehicle and to assign a serial number to the vehicle. Starting in 1981 the Vehicle Identification Numbers were required to conform to an international standard. For vehicles built prior to 1981 one may consult the National Automobile Theft Bureau’s publication Passenger Vehicle Identification Manual for the year in question. Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V13. This data element also appears in the Parkwork data file as PVIN.",000000000000,"No VIN Required,Not a Vehicle for Road Use",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",119,Sport Utility Truck (SUT),NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",128,Ambulance,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",129,Street Sweeper,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",130,Fire Apparatus,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",4,Low Speed Vehicle (LSV) / Neighborhood Electric Vehicle (NEV),NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",66,Truck-Tractor,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",7,Sport Utility Vehicle (SUV)/Multi-Purpose Vehicle (MPV),NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,ICFINALBODY,icfinalbody,Final Stage Body Class,This element captures the completed/finished body class for an incomplete vehicle. An incomplete vehicle is completed by a final stage manufacturer. The intent of this data element is to capture the body class for incomplete vehicles when they are finished for road use.,"This data element is only applicable to incomplete vehicles, and the attributes are a subset of the vPIC Body Class attributes. Information captured in this data element is based on the police crash report. This data element also appears in the Person data file and in the Parkwork data file as PICFINALBODY.",73,Bus - School Bus,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,TRLR1VIN,trlr1vin,Trailer VIN (1),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",000000000000,"No VIN Required,Not a Vehicle for Road Use",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,TRLR2VIN,trlr2vin,Trailer VIN (2),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",000000000000,"No VIN Required,Not a Vehicle for Road Use",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,TRLR3VIN,trlr3vin,Trailer VIN (3),This data element records the vehicle identification number (VIN) of any trailing units of a combination vehicle.,"Prior to 2018, if a character of the VIN is missing or undecipherable, the VIN length will be less than 12 characters. Starting in 2018 an asterisk (*) is used for missing or undecipherable VIN characters. Prior to 2020 the Data Element ID was V15. These data elements also appear in the Parkwork data file as PTRLR1VIN, PTRLR2VIN, and PTRLR3VIN.",000000000000,"No VIN Required,Not a Vehicle for Road Use",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,19,"Vehicle More Than 10,000 lbs., Other",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,V_CONFIG,v_config,Vehicle Configuration,This data element describes the general configuration of this vehicle if applicable.,Prior to 2016 the Data Element ID was V18. From 2016 to 2019 the Data Element ID was V19. This data element also appears in the Parkwork data file as PV_CONFIG.,88,"Qualifying Vehicle, Unknown Configuration",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,0,No Special Use Noted,NA,NA,NA,NA,NA,NA,NA,1,1,NA
FARS,vehicle,UNDEROVERRIDE,underoverride,Vehicle Underride/Override,This element indicates whether this vehicle experienced an underride or override with another vehicle during the crash.,This data element also appears in the Parkwork data file as PUNDEROVERRIDE.,0,No Underride or Override,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,UNDEROVERRIDE,underoverride,Vehicle Underride/Override,This element indicates whether this vehicle experienced an underride or override with another vehicle during the crash.,This data element also appears in the Parkwork data file as PUNDEROVERRIDE.,1,Underride,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,UNDEROVERRIDE,underoverride,Vehicle Underride/Override,This element indicates whether this vehicle experienced an underride or override with another vehicle during the crash.,This data element also appears in the Parkwork data file as PUNDEROVERRIDE.,2,Override,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,UNDEROVERRIDE,underoverride,Vehicle Underride/Override,This element indicates whether this vehicle experienced an underride or override with another vehicle during the crash.,This data element also appears in the Parkwork data file as PUNDEROVERRIDE.,7,Not Applicable,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,UNDEROVERRIDE,underoverride,Vehicle Underride/Override,This element indicates whether this vehicle experienced an underride or override with another vehicle during the crash.,This data element also appears in the Parkwork data file as PUNDEROVERRIDE.,8,Not Reported,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,UNDEROVERRIDE,underoverride,Vehicle Underride/Override,This element indicates whether this vehicle experienced an underride or override with another vehicle during the crash.,This data element also appears in the Parkwork data file as PUNDEROVERRIDE.,9,Reported as Unknown,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20407,Chevrolet Blazer,NA,NA,NA,NA,NA,NA,NA,1,NA,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",35883,Nissan/Datsun Medium/Heavy - COE high entry,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",41035,Mazda 323/GLC/ Protege/ Protege 5,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of First Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2021,2021,NA,NA,NA,NA,NA,NA,NA,1,NA,NA
FARS,vehicle,LAST_YR,last_yr,"Date of Last Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2021,2021,NA,NA,NA,NA,NA,NA,NA,1,NA,NA
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,17,Crossing Over (Passing Through) Junction,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,vehicle,P_CRASH2,p_crash2,Critical Event - Precrash  (Event),"This data element identifies the attribute that best describes the critical event that made this crash imminent (i.e., something occurred that made the collision possible).",NA,64,"From Parking Lane/Shoulder, Median/Crossover, Roadside",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,person,REST_MIS,rest_mis,Indication of Restraint System Misuse?,This data element identifies any misuse of the available restraint system used by this person.,"Prior to 2019 this data element’s name was “Indication of Misuse of Restraint System/Helmet” that included helmet misuse, and the Data Element ID was P11. Starting in 2019 helmet misuse is captured as part of the data element “Indication of Helmet Misuse.”",0,No Indication of Misuse,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,person,REST_MIS,rest_mis,Indication of Restraint System Misuse?,This data element identifies any misuse of the available restraint system used by this person.,"Prior to 2019 this data element’s name was “Indication of Misuse of Restraint System/Helmet” that included helmet misuse, and the Data Element ID was P11. Starting in 2019 helmet misuse is captured as part of the data element “Indication of Helmet Misuse.”",1,"Yes, Indication of Misuse",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,person,REST_MIS,rest_mis,Indication of Restraint System Misuse?,This data element identifies any misuse of the available restraint system used by this person.,"Prior to 2019 this data element’s name was “Indication of Misuse of Restraint System/Helmet” that included helmet misuse, and the Data Element ID was P11. Starting in 2019 helmet misuse is captured as part of the data element “Indication of Helmet Misuse.”",7,None Used/Not Applicable,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,person,REST_MIS,rest_mis,Indication of Restraint System Misuse?,This data element identifies any misuse of the available restraint system used by this person.,"Prior to 2019 this data element’s name was “Indication of Misuse of Restraint System/Helmet” that included helmet misuse, and the Data Element ID was P11. Starting in 2019 helmet misuse is captured as part of the data element “Indication of Helmet Misuse.”",8,Not a Motor Vehicle Occupant,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,person,HELM_MIS,helm_mis,Indication of Helmet Misuse?,This data element identifies any misuse of the helmet used by this person.,"This data element is applicable to occupants of body types 80-91, 96, and 97. Prior to 2019 this data was collected as part of the data element “Indication of Misuse of Restraint System/Helmet,” and the Data Element ID was P11.",0,No Indication of Misuse,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,person,HELM_MIS,helm_mis,Indication of Helmet Misuse?,This data element identifies any misuse of the helmet used by this person.,"This data element is applicable to occupants of body types 80-91, 96, and 97. Prior to 2019 this data was collected as part of the data element “Indication of Misuse of Restraint System/Helmet,” and the Data Element ID was P11.",1,"Yes, Indication of Misuse",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,person,HELM_MIS,helm_mis,Indication of Helmet Misuse?,This data element identifies any misuse of the helmet used by this person.,"This data element is applicable to occupants of body types 80-91, 96, and 97. Prior to 2019 this data was collected as part of the data element “Indication of Misuse of Restraint System/Helmet,” and the Data Element ID was P11.",7,None Used/Not Applicable,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,person,HELM_MIS,helm_mis,Indication of Helmet Misuse?,This data element identifies any misuse of the helmet used by this person.,"This data element is applicable to occupants of body types 80-91, 96, and 97. Prior to 2019 this data was collected as part of the data element “Indication of Misuse of Restraint System/Helmet,” and the Data Element ID was P11.",8,Not a Motor Vehicle Occupant,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,person,ALC_DET,alc_det,Method of Alcohol Determination by Police,NA,NA,6,"Breath Test, Unknown Type",NA,NA,NA,NA,NA,NA,NA,1,NA,NA
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2022,2022,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,person,LOCATION,location,Non-Motorist Location at Time of Crash,This data element identifies the attribute that best describes the location of this non-motorist with respect to the roadway at the time of the crash.,Prior to 2022 the Element Data ID was NM10.,2,At Intersection - In Unmarked / Unknown if Marked Crosswalk,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",10,Emergency Vehicle Related,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",6,Deaf/Hard of Hearing,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,drimpair,DRIMPAIR,drimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this driver that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material--in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Driver Level” is now captured under this new data element.",7,Blind/Low Vision,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",13,"Person with an Intellectual, Cognitive, or Developmental Disability",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",23,Failure to Dim Lights or to Have Lights on When Required,NA,NA,NA,NA,NA,NA,NA,1,NA,NA
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",86,"Pedestrian, Pedalcyclist, or Other Non-Motorist",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,741,"Dash - Run, No Visual Obstruction Noted",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,pbtype,PEDCTYPE,pedctype,Pedestrian Crash Type,This data element summarizes the circumstances of the crash for this pedestrian.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB30.,742,Dart-Out - Visual Obstruction Noted,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,231,Motorist Overtaking - Undetected Bicyclist or Detected - Too Late to Avoid,NA,NA,NA,NA,NA,NA,NA,1,1,NA
FARS,pbtype,PEDCGP,pedcgp,Pedestrian Crash Group,This data element provides general groupings of the more specific individual Pedestrian Crash Types.,This data element is applicable to pedestrians only. Prior to 2022 the Element Data ID was NM9- PB38.,740,"Dash - Run, No Visual Obstruction Noted / Dart-Out - Visual Obstruction Noted",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,nmcrash,NMCC,nmcc,Non-Motorist Contributing Circumstances,This data element describes the actions and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances at Time of Crash.” Prior to 2022 the Element Data ID was NM12.",92,Contributing Circumstance - No Details,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",6,Deaf/Hard of Hearing,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,nmimpair,NMIMPAIR,nmimpair,Condition (Impairment) at Time of Crash,This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.,"This data element attempts to identify physical impairments to this non-motorist that may have contributed to the cause of the crash. These impairments can appear anywhere in the case material—in the narrative section, in the violations section, in a column entitled “Contributing Factors” or “Driver Action,” etc. Some information that had been collected under “Related Factors—Person Level” is now captured under this new data element. Prior to 2019 the Data Element ID was NM14. From 2019-2021 the Element Data ID was NM15.",7,Blind/Low Vision,NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",395,"Depressants, Type Unknown",NA,NA,NA,NA,NA,NA,NA,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",595,"Hallucinogens, Type Unknown",NA,NA,NA,NA,NA,NA,NA,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",695,"Cannabinoid, Type Unknown",NA,NA,NA,NA,NA,NA,NA,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",706,"Pyrrolidine (PCPy,PHP,TCPy)",NA,NA,NA,NA,NA,NA,NA,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",795,"PCP, Type Unknown",NA,NA,NA,NA,NA,NA,NA,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",903,"Petroleum Products (gasoline, kerosene)",NA,NA,NA,NA,NA,NA,NA,1,NA,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",995,"Inhalants, Type Unknown",NA,NA,NA,NA,NA,NA,NA,1,NA,NA
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",8,"Person with an Intellectual, Cognitive, or Developmental Disability",NA,NA,NA,NA,NA,NA,NA,1,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",56,Non-Operator Flees Scene,NA,NA,NA,NA,NA,NA,NA,1,1,NA
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",82,"Pedestrian, Pedalcyclist, or Other Non-Motorist",NA,NA,NA,NA,NA,NA,NA,1,1,NA
FARS,vehicle,BODY_TYP,body_typ,NCSA Body Type,"This data element identifies a classification of this vehicle based on its general body configuration, size, shape, doors, etc. as defined by NCSA.","This data element also appears in the Person data file and in the Parkwork data file as PBODYTYP. 1975-1981: Within the yearly NHTSA report Fatal Accident Reporting System, the term ""Light Trucks"" includes Vans. The body type data do not track with the original documentation. For example, documentation states that BODY_TYP EQ 7 is for utility vehicles. However, when the data files are examined, one sees that BODY_TYP EQ 43 is the value that will provide the desired result. The data files have been modified to make the early years for this data element compatible with 1981. Utility vehicles are also part of the light truck category. BODY_TYP 40, large limousines, are not included as part of Passenger Cars or Passenger Vehicles. 1982-1990: Within the yearly NHTSA report Fatal Accident Report System, the term “Light Truck” includes Vans. Utility vehicles are also part of the light-truck category. BODY_TYP 13, large limousines and BODY_TYP 14, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. A single-unit truck that tows another vehicle, or a bobtail by itself, is considered a combination truck. 1991-Later: Within the yearly NHTSA publication Traffic Safety Facts, the term ""Light Trucks"" includes Vans. BODY_TYP 12, large limousines and BODY_TYP 13, three-wheel automobiles or automobile derivatives, are not included as part of Passenger Cars or Passenger Vehicles. When defining School Buses 1993 and later be sure to include the new body type 24 (van-based school bus). However, body type 24 is not part of Buses. When defining Transit Buses 1993 and later be sure to include the new body type 25 (van-based transit bus). However, body type 25 is not part of Buses. A single-unit truck that tows another vehicle, or a bobtail, is considered a combination truck. Prior to 2020 this data element’s name was ""Body Type"" and the Data Element ID was V11.",81,Moped,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",0,No Trailers,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",1,One Trailer,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",2,Two Trailers,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",3,Three or More Trailers,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",4,"Yes, Number of Trailers  Unknown",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,TOW_VEH,tow_veh,Vehicle Trailing,This data element identifies whether this vehicle had any attached trailing units or was towing another motor vehicle.,"Trailing unit applies to any device connected to a motor vehicle by a hitch, including tractor- trailer combinations, a single-unit truck pulling a trailer (truck trailer), a boat trailer hitched onto a motor vehicle, etc. Note that the number of unknowns is 0 until 1982. From 1982 to 1984 the number of unknowns is approximately 2,500 per year. Starting in 1985 the number of unknowns falls to about 300 per year. Prior to 2020 the Data Element ID was V14. This data element also appears in the Person data file and in the Parkwork data file as PTRAILER.",7,Trailing Unit Other than a Trailer or Another Motor Vehicle,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,BUS_USE,bus_use,Bus Use,This data element describes the common type of bus service this vehicle was being used as at the time of the crash or the primary use for the bus if not in service at the time of the crash.,Prior to 2016 the Data Element ID was V21. From 2016 to 2019 the Data Element ID was V22. This data element also appears in the Parkwork data file as PBUS_USE.,97,"Bus, Unknown Use",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,ROLLOVER,rollover,Rollover Type,This data element identifies this vehicle’s involvement in a rollover or overturn during the crash. Rollover is defined as any vehicle rotation of 90° or more about any true longitudinal or lateral axis. Rollover can occur at any time during the crash.,Data are not available from 1975 to 1977. Prior to 2016 the Data Element ID was V26. From 2016 to 2019 the Data Element ID was V27. Starting in 2022 this data element is derived from the “Sequence of Events” data element for each vehicle with an event equal to 01. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. This data element also appears in the Person data file.,NA,"Rollover, Tripped by Object/Vehicle",NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,vehicle,ROLLOVER,rollover,Rollover Type,This data element identifies this vehicle’s involvement in a rollover or overturn during the crash. Rollover is defined as any vehicle rotation of 90° or more about any true longitudinal or lateral axis. Rollover can occur at any time during the crash.,Data are not available from 1975 to 1977. Prior to 2016 the Data Element ID was V26. From 2016 to 2019 the Data Element ID was V27. Starting in 2022 this data element is derived from the “Sequence of Events” data element for each vehicle with an event equal to 01. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. This data element also appears in the Person data file.,9,"Rollover, Unknown Type*/",NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,vehicle,ROLLOVER,rollover,Rollover Type,This data element identifies this vehicle’s involvement in a rollover or overturn during the crash. Rollover is defined as any vehicle rotation of 90° or more about any true longitudinal or lateral axis. Rollover can occur at any time during the crash.,Data are not available from 1975 to 1977. Prior to 2016 the Data Element ID was V26. From 2016 to 2019 the Data Element ID was V27. Starting in 2022 this data element is derived from the “Sequence of Events” data element for each vehicle with an event equal to 01. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. This data element also appears in the Person data file.,3,Rollover,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,vehicle,ROLLOVER,rollover,Rollover Type,This data element identifies this vehicle’s involvement in a rollover or overturn during the crash. Rollover is defined as any vehicle rotation of 90° or more about any true longitudinal or lateral axis. Rollover can occur at any time during the crash.,Data are not available from 1975 to 1977. Prior to 2016 the Data Element ID was V26. From 2016 to 2019 the Data Element ID was V27. Starting in 2022 this data element is derived from the “Sequence of Events” data element for each vehicle with an event equal to 01. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. This data element also appears in the Person data file.,8,Not Applicable,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,vehicle,ROLINLOC,rolinloc,Location of Rollover,This data element identifies the location of the trip point or start of this vehicle’s roll.,Prior to 2016 the Data Element ID was V27. From 2016 to 2019 the Data Element ID was V28.,8,Not Applicable,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,DEFORMED,deformed,Extent of Damage,This data element records the amount of damage sustained by this vehicle as indicated in the case material based on an operational damage scale.,The data on 8 (Not Reportable) collected in 1976 are no longer contained in the data file. The data for that year are not consistent with the documentation of the time. The data element name was “Extent of Deformation” from 1975 to 2008. The data element’s name was changed to “Extent of Damage” in 2009. Prior to 2016 the Data Element ID was V29. From 2016 to 2019 the Data Element ID was V30. This data element also appears in the Parkwork Data File as PVEH_SEV.,7,"Damage Reported, Extent Unknown",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,TOWED,towed,Vehicle Towed,NA,NA,NA,Towed Due to Disabling Damage,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,vehicle,TOWED,towed,Vehicle Towed,NA,NA,3,Towed But Not Due to Disabling Damage,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,vehicle,TOWED,towed,Vehicle Towed,NA,NA,5,Not Towed,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,TOWED,towed,Vehicle Towed,NA,NA,7,"Towed, Unknown Reason",NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,vehicle,TOWED,towed,Vehicle Towed,NA,NA,8,Not Reported,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,TOWED,towed,Vehicle Towed,NA,NA,9,Reported as Unknown*/,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,vehicle,TOWED,towed,Vehicle Towed,NA,NA,6,Towed,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,TOWED,towed,Vehicle Towed,NA,NA,9,Reported as Unknown,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",0,No Record,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",1,January,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",2,February,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",3,March,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",4,April,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",5,May,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",6,June,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",7,July,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",8,August,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",9,September,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",10,October,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",11,November,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",12,December,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",98,No Driver Present/Unknown if Driver Present,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_MO,first_mo,"Date of Oldest Crash, Suspension or Conviction (Month)","This data element records the month of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of First Crash, Suspension, or Conviction.""",99,Unknown,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",0,No Record,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2005,2005,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2006,2006,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2009,2009,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2010,2010,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2011,2011,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2012,2012,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2013,2013,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2014,2014,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2015,2015,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2016,2016,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2017,2017,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2018,2018,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2019,2019,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2020,2020,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2021,2021,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2022,2022,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",9998,No Driver Present/Unknown if Driver Present,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",9999,Unknown,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",0,No Record,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",1,January,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",2,February,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",3,March,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",4,April,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",5,May,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",6,June,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",7,July,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",8,August,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",9,September,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",10,October,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",11,November,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",12,December,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",98,No Driver Present/Unknown if Driver Present,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_MO,last_mo,"Date of Most Recent Crash, Suspension or Conviction (Month)","This data element records the month of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Month of Last Crash, Suspension, or Conviction.""",99,Unknown,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",0,No Record,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2005,2005,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2006,2006,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2009,2009,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2010,2010,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2011,2011,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2012,2012,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2013,2013,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2014,2014,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2015,2015,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2016,2016,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2017,2017,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2018,2018,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2019,2019,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2020,2020,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2021,2021,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2022,2022,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",9998,No Driver Present/Unknown if Driver Present,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",9999,Unknown,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehicle,VTRAFWAY,vtrafway,Trafficway Description,This data element identifies the attribute that best describes the trafficway flow just prior to this vehicle’s critical precrash event.,In 2010 this data element was no longer collected at the Accident level. It is now collected at the Vehicle level.,7,"Two-Way Divided, Unknown if Unprotected Median or Positive Median Barrier",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,7,Other Pedalcyclist,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,8,Person on a Personal Conveyance,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,10,Person In/On a Building,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,NA,Person on Motorized Personal Conveyance,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,person,PER_TYP,per_typ,Person Type,This data element describes the role of this person or non-motorist at the time they became involved in the crash.,NA,13,"Person on Personal Conveyance, Unknown if Motorized or Non-Motorized*/",NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,person,DEVTYPE,devtype,Non-Motorist Device Type,This element describes the type of transport device operated by the non-motorist.,NA,0,Not Applicable,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,DEVTYPE,devtype,Non-Motorist Device Type,This element describes the type of transport device operated by the non-motorist.,NA,1,"Ridden Animal, Animal Drawn Conveyance, or Trailer",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,DEVTYPE,devtype,Non-Motorist Device Type,This element describes the type of transport device operated by the non-motorist.,NA,2,Railway Vehicle or Road Vehicle on Rails,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,DEVTYPE,devtype,Non-Motorist Device Type,This element describes the type of transport device operated by the non-motorist.,NA,3,Bicycle,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,DEVTYPE,devtype,Non-Motorist Device Type,This element describes the type of transport device operated by the non-motorist.,NA,4,Other Pedalcycle,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,DEVTYPE,devtype,Non-Motorist Device Type,This element describes the type of transport device operated by the non-motorist.,NA,5,Mobility Aid Device,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,DEVTYPE,devtype,Non-Motorist Device Type,This element describes the type of transport device operated by the non-motorist.,NA,6,Skates,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,DEVTYPE,devtype,Non-Motorist Device Type,This element describes the type of transport device operated by the non-motorist.,NA,7,Non-Self-Balancing Board (Skateboard),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,DEVTYPE,devtype,Non-Motorist Device Type,This element describes the type of transport device operated by the non-motorist.,NA,8,Self-Balancing Board,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,DEVTYPE,devtype,Non-Motorist Device Type,This element describes the type of transport device operated by the non-motorist.,NA,9,Standing or Seated Scooter,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,DEVTYPE,devtype,Non-Motorist Device Type,This element describes the type of transport device operated by the non-motorist.,NA,97,"Personal Conveyance, Other",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,DEVTYPE,devtype,Non-Motorist Device Type,This element describes the type of transport device operated by the non-motorist.,NA,98,"Personal Conveyance, Unknown Type",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,DEVTYPE,devtype,Non-Motorist Device Type,This element describes the type of transport device operated by the non-motorist.,NA,99,Unknown Type of Non-Motorist,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,person,DEVMOTOR,devmotor,Non-Motorist Device Motorization,This element describes the motorization of the device operated by the non-motorist.,NA,NA,(Self-evident),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",0,None Noted,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",17,Stopped Vehicle Set in Motion by Non-Driver,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",NA,Reported as Unknown*/,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",0,None Noted,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",29,Default Code Used for Vehicle Numbering,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",30,Multi-Wheeled Motorcycle Conversion,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",32,Vehicle Registration for a Person with a Disability,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",33,Vehicle Being Pushed by Non-Motorist,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",35,Reconstructed/Altered Vehicle,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",37,Transporting Children To/From Head Start/Day Care,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",39,"Highway Construction, Maintenance, or Utility Vehicle, In Transport (Inside or Outside Workzone)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",41,"Police, Fire, or EMS Vehicle Working at the Scene of an Emergency or Performing Other Traffic Control Activities",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",42,"Other Working Vehicle (Not Construction, Maintenance, Utility, Police, Fire, or EMS Vehicle)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",44,Adaptive Equipment,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",45,Slide-in Camper,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",NA,Reported as Unknown*/,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",0,None Noted,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",29,Default Code Used for Vehicle Numbering,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",30,Multi-Wheeled Motorcycle Conversion,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",32,Vehicle Registration for a Person with a Disability,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",33,Vehicle Being Pushed by Non-Motorist,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",35,Reconstructed/Altered Vehicle,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",37,Transporting Children To/From Head Start/Day Care,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",39,"Highway Construction, Maintenance, or Utility Vehicle, In Transport (Inside or Outside Workzone)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",41,"Police, Fire, or EMS Vehicle Working at the Scene of an Emergency or Performing Other Traffic Control Activities",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",42,"Other Working Vehicle (Not Construction, Maintenance, Utility, Police, Fire, or EMS Vehicle)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",44,Adaptive Equipment,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",45,Slide-in Camper,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",NA,Reported as Unknown*/,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",0,None Noted,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",NA,Reported as Unknown*/,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,7,Other Pedalcyclist,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,8,Person on a Personal Conveyance,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,10,Person In/On a Building,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,NA,Person on Motorized Personal Conveyance,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,pbtype,PBPTYPE,pbptype,Person Type,This data element describes the role of this person involved in the crash.,NA,13,"Person on Personal Conveyance, Unknown if Motorized or Non-Motorized*/",NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,pbtype,BIKECGP,bikecgp,Bicyclist Crash Group,This data element provides general groupings of the more specific individual Bicyclist Crash Types.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB38B.,240,Bicyclist Overtaking Motor Vehicle,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1001,"1-Cyclohexyl-4-(1,2-diphenylethyl) piperazine (MT-45)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1002,"3,4-dichloro-N-[2-(dimethylamino)cyclohexyl]-N-methylbenzamide (U-47700)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1003,"3,4-Dichloro-N- [(1-dimethyl- amino) cyclohexylmethyl]- benzamide (AH-7921)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1004,3-Methylthiofentanyl (Methylthiofentanyl),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1005,4-Fluorofentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1006,5-methyldihydromorphone (Metopon),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1007,Acetorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1008,Acetyl Fentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1009,Acetyl-alpha-methylfentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1010,Acetyldihydrocodeine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1011,Acetylmethadol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1012,Alfentanil,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1013,Allylprodine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1014,Alphacetylmethadol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1015,Alpha-meprodine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1016,Alphamethadol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1017,Alpha-Methylfentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1018,Alphamethythiofentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1019,Alphaprodine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1020,Anileridine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1021,Benzylmorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1022,Betacetylmethadol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1023,Beta-Hhydroxy-3-methylfentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1024,Beta-hydroxyfentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1025,Beta-hydroxythiofentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1026,Beta-meprodine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1027,Betamethadol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1028,Betaprodine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1029,Bezitramide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1030,Buprenorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1031,Butorphanol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1032,Butyryl Fentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1033,Carfentanil,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1034,Clonitazene,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1035,Codeine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1036,Cyprenorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1037,Desomorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1038,Dextromoramide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1039,Propoxyphene (dextropropoxyphene),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1040,Diacetylmorphine (Heroin),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1041,Diampromide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1042,Diethylthiambutene,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1043,Difenoxin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1044,Dihydrocodeine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1045,Dihydroetrophine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1046,Dihydromorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1047,Dimenoxadol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1048,Dimepheptanol (Racemethadol),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1049,Dimethylthiambutene,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1050,Dioxaphetyl Butyrate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1051,Diphenoxylate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1052,Dipipanone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1053,Diprenorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1054,Ethylmethylthiambutene,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1055,Ethylmorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1056,Etonitazene,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1057,Etorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1058,Etoxeridine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1059,Fentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1060,Furethidine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1061,Hydrocodone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1062,Hydromorphinol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1063,Hydromorphone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1064,Hydroxypethidine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1065,Isomethadone (isoamidone),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1066,Ketobemidone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1067,Levo-alphacetylmethadol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1068,Levomethorphan,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1069,Levomoramide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1070,Levophenacylmorphan,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1071,Levorphanol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1072,Meperidine (Pethidine),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1073,Metazocine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1074,Methadone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1075,Methyldesorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1076,Methyldihydromorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1077,3-Methylfentanyl (Methylfentanyl; cis-3-methylfentanyl; trans-3-methylfentanyl),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1078,Methyl-phenyl-propionoxypiperidine (MPPP),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1079,6-Monoacetylmorphine (6-Acetylmorphine; 6-MAM; 6-AM; Heroin metabolite),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1080,Moramide - intermediate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1081,Morpheridine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1082,Morphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1083,Morphine-Free,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1084,Myrophine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1085,Nalorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1086,Norbuprenorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1087,Norlevorphanol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1088,Normeperidine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1089,Normethadone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1090,Normorphine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1091,Norpipanone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1092,Norpropoxyphene,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1093,Oripavine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1094,Oxycodone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1095,Oxymethebanol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1096,Oxymorphone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1097,Papaverine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1098,Para-fluorofentanyl (4-Fluorofentanyl; pFF),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1099,Pentazocine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1100,Phenadoxone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1101,Phenampromide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1102,Phenazocine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1103,Phenomorphan,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1104,Phenylethyl-phenyl-acetoxypiperidine (PEPAP),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1105,Pholcodine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1106,Piritramide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1107,Proheptazine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1108,Properidine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1109,Propiram,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1110,Remifentanil,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1111,Sufentanil,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1112,Tapentadol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1113,Thebacon,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1114,Thebaine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1115,Thiofentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1116,Tilidine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1117,Tramadol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1118,Trimeperidine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1119,2-fluorofentanyl (ortho-fluorofentanyl),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1120,"3,4-dichloro-N-[2-(diethylamino)cyclohexyl]-N-methylbenzamide (U-49900)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1121,"3,4-dichloro-N-[2-(dimethylamino)cyclohexyl]-N-methyl-benzeneacetamide (U-51754)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1122,3-Methylmethoxyacetylfentanyl (meta-Methylmethoxyacetylfentanyl),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1123,4-anilino-N-phenethylpiperidine (4-ANPP; 4-aminophenyl-1-phenethylpiperidine; Despropionyl fentanyl),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1124,4F-butyrylfentanyl (para-fluorobutyrylfentanyl),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1125,4F-isobutyrylfentanyl (para-fluoroisobutyrylfentanyl; FIBF),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1126,4-methylmethoxyacetylfentanyl (para-methylmethoxyacetylfentanyl),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1127,Acryl Fentanyl (Acryloylfentanyl),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1128,Cyclopropylfentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1129,Desmethyltramadol (O-desmethyltramadol),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1130,Furanylfentanyl (2-furanylfentanyl),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1131,Isobutyrylfentanyl (Isobutyrfentanyl),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1132,Methoxyacetylfentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1133,Mitragynine (kratom),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1134,Tetrahydrofuranyl fentanyl (THF-F),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1135,Valeryl fentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1136,Norfentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1137,"2-ethylene-1,5-dimethyl-3,3-diphenylpyrrolidine [EDDP]",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1997,"Narcotic Analgesics, Type Unknown",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2001,7-Amino-clonazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2002,Acebutolol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2003,Acetazolamide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2004,Alpha-hydroxyalprazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2005,Alprazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2006,Amantadine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2007,Amitriptyline,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2008,Amobarbital,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2009,Amoxapine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2010,Aprobarbital,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2011,Aripiprazole,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2012,Atenolol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2013,Atropine (HEART RHYTHM),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2014,Barbital,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2015,Benzylfentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2016,Brivaracetam (BRV; UCB-34714; Briviact),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2017,Bromazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2018,Brompheniramine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2019,Bupivacaine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2020,Bupropion,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2021,Buspirone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2022,Butabarbital,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2023,Butalbital,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2024,Butobarbital (butethal),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2025,Camazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2026,Carisoprodol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2027,Cetirizine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2028,Chloral betaine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2029,Chloral Hydrate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2030,Chlordiazepoxide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2031,Chlorhexadol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2032,Chloroquine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2033,Chlorothiazide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2034,Chlorpheniramine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2035,Chlorpromazine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2036,Chlorzoxazone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2037,Citalopram,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2038,Clemastine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2039,Clobazam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2040,Clomipramine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2041,Clonazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2042,Clonazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2043,Clonidine-(FOR HIGH BLOOD PRESSURE & ADHD),NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2044,Clorazepate Dipotassium,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2045,Clotiazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2046,Cloxazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2047,Clozapine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2048,Cyclobenzaprine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2049,Delorazepam (chlordesmethyldiazepam; nordiclazepam),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2050,Desalkylflurazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2051,Deschloroetizolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2052,Desipramine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2053,Desmethylcitalopram (Norcitalopram),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2054,Desmethylclomipramine (Norclomipramine),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2055,Desmethyldoxepin (Nordoxepin),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2056,Desmethylsertraline (Norsertraline),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2057,Desmethyltrimipramine (Nortrimipramine),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2058,Dexfenfluramine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2059,Dextromethorphan,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2060,Dextrorphan,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2061,Diazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2062,Diclazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2063,Diphenhydramine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2064,Donepezil,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2065,Doxepin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2066,Doxylamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2067,Droperidol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2068,Duloxetine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2069,Embutramide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2070,Escitalopram,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2071,Estazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2072,Eszopiclone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2073,Ethchlorvynol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2074,Ethinamate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2075,Ethosuximide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2076,Ethotoin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2077,Ethyl Ioflazepate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2078,Etizolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2079,Felbamate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2080,Flubromazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2081,Flubromazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2082,Fludiazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2083,Flunitrazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2084,Fluoxetine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2085,Flurazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2086,Fluvoxamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2087,Fosphenytoin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2088,Gabapentin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2089,Gamma-Hydroxybutyric Acid (GHB),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2090,Glutethimide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2091,Guaifenesin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2092,Halazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2093,Haloperidol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2094,Haloxazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2095,Hexobarbital,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2096,Hydroxyzine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2097,Imipramine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2098,Isocarboxazid,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2099,Isopropanol,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2100,Ketazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2101,Lamotrigine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2102,Levetiracetam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2103,Levocetirizine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2104,Levodopa,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2105,Lithium,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2106,Loprazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2107,Lorazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2108,Lormetazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2109,Loxapine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2110,Lurasidone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2111,Maprotiline,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2112,Mebutamate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2113,Meclizine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2114,Meclonazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2115,Mecloqualone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2116,Medazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2117,Mefloquine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2118,Memantine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2119,Mephenytoin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2120,Mephobarbital (Methylphenobarbital),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2121,Mepivacaine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2122,Meprobamate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2123,Mesoridazine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2124,Metaxalone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2125,Methanol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2126,Methaqualone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2127,Metharbital,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2128,Methohexital,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2129,Methyprylon,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2130,Metoclopramide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2131,Metoprolol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2132,Midazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2133,Mirtazapine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2134,Molindone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2135,Nefazodone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2136,Nifedipine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2137,Nimetazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2138,Nitrazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2139,Nordiazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2140,Norfluoxetine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2141,Norsertraline,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2142,Nortriptyline,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2143,Norvenlafaxine; O- Desmethylvenlafaxine (Desvenlafaxine; Norvenlafaxine),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2144,Olanzapine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2145,Orphenadrine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2146,Oxazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2147,Oxazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2148,Oxcarbazepine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2149,Paliperidone; (also: 9-Hydroxyrisperidone),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2150,Paraldehyde,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2151,Paroxetine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2152,Pentobarbital,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2153,Petrichloral,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2154,Phenazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2155,Phencyclohexylamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2156,Phenelzine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2157,Pheniramine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2158,Phenobarbital,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2159,Phenytoin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2160,Pinazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2161,Prazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2162,Pregabalin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2163,Procainamide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2164,Prochlorperazine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2165,Procyclidine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2166,Promazine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2167,Promethazine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2168,Propranolol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2169,Protriptyline,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2170,Pyrazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2171,Pyrilamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2172,Quazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2173,Quetiapine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2174,Quinidine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2175,Quinine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2176,Ramelteon,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2177,Risperidone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2178,Secobarbital,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2179,Selegiline,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2180,Sertraline,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2181,Sulfondiethylmethane,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2182,Sulfonethylmethane,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2183,Sulfonmethane,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2184,Talbutal,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2185,Temazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2186,Tetrazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2187,Thenylfentanyl,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2188,Thiamylal,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2189,"Thiopental (Pentothal, Sodium Pentothal)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2190,Thioridazine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2191,Thiothixene,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2192,Tiagabine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2193,Tiletamine (Telazol),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2194,Tizanidine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2195,Topiramate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2196,Tranylcypromine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2197,Trazodone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2198,Trichloroethanol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2199,Trifluoperazine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2200,Trifluopromazine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2201,Trimethadione,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2202,Trimipramine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2203,Tripelennamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2204,Triprolidine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2205,Triazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2206,Tybamate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2207,Valproic Acid,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2208,Venlafaxine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2209,Verapamil,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2210,Vilazodone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2211,Zaleplon,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2212,Ziprasidone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2213,Zolazepam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2214,Zolpidem,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2215,Zopiclone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2216,Benzodiazepine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2217,Barbiturates,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2218,Xylazine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2219,Rocuronium [Zemuron],NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2220,Isopropanol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2221,Acetone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2222,Hydroxybupropion,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2223,8-Aminoclonazolam,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2997,"Depressants, Type Unknown",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3001,1-(4-methylbenzyl)piperazine (MBZP),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3002,"1,4-dibenzylpiperazine (DBZP)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3003,"3,4-methylendioxy-alpha-pyrrolidinobutiophenone (MDPBP)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3004,"3,4-methylenedioxy-alpha-pyrrolidinopropiophenone (MDPPP)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3005,"3.4-dimethyllmethcathinone (3,4-DMMC)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3006,3-fluorophenmetrazine (3-FPM),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3007,3-trifluoromethylphenypiperazine (TFMPP),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3008,4-bromomethcathinone (brephedrone),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3009,4-methoxy-alpha-pyrrolidinopropiophenone (MeOPPP),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3010,4-methyl-alpha-pyrrolidinobutiophenone (MBPB),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3011,4-methyl-alpha-pyrrolidinohexiophenone (MPHP),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3012,4-methyl-ethcathinone (4-MEC),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3013,4-methylthioamphetamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3014,Alpha-pyrrolidinobutiophenone (alpha-PBP),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3015,Alpha-Pyrrolidinopentiophenone (alpha-PVP; Flakka),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3016,Alpha-pyrrolidinopentiothiophenone (alpha-PVT),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3017,Alpha-pyrrolidinopropiophenone (alpha-PPP),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3018,Aminorex,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3019,Amphetamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3020,Armodafinil,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3021,Atomoxetine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3022,Benzoylecgonine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3023,Benzphetamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3024,Benztropine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3025,Butylone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3026,Caffeine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3027,Cathine (Norpseudoephedrine),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3028,Cathinone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3029,Chlorphentermine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3030,Clephedrone (4-chloromethcathinone; 4-CMC),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3031,Clortermine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3032,Cocaethylene,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3033,Cocaine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3034,Cotinine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3035,Dextroamphetamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3036,Dichloralphenazone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3037,Diethylpropion,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3038,Doxapram,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3039,Ecgonine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3040,Ephedrine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3041,Ethylethcathinone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3042,Ethylphenidate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3043,Fencamfamin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3044,Fenethylline,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3045,Fenfluramine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3046,Fenproporex,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3047,Fluoroamphetamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3048,Fluoromethamphetamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3049,Lisdexamfetamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3050,Mazindol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3051,Mefenorex,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3052,Mephedrone (4-methylmethcathinone),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3053,Methamphetamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3054,Methcathinone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3055,Methedrone (4-methoxymethcathinone),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3056,Methiopropamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3057,Methylenedioxypyrovalerone (MDPV),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3058,Methylone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3059,Methylphenidate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3060,Modafinil,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3061,"N, N-Dimethylamphetamine (Dimethylamphetamine)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3062,Naphyrone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3063,N-Benzylpiperazine (BZP; 1-Benzylpiperazine),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3064,N-ethyl pentylone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3065,N-Ethylamphetamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3066,Nicotine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3067,Norepinephrine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3068,para-methoxyphenylpiperazine (MeOPP),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3069,Pentedrone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3070,Pentylone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3071,Phendimetrazine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3072,Phenmetrazine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3073,Phentermine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3074,Phenylpropanolamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3075,Pipradrol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3076,Propylhexedrine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3077,Pseudoephedrine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3078,Pyrovalerone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3079,Vinbarbital,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3080,Ecgonine Methyl Ester,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3081,Norcocaine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3082,Methylecgonine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3997,"Stimulant, Type Unknown",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4001,"2-(2,5-Dimethoxy-4-(n)-propylphenyl) ethanamine (2C-P)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4002,"2-(2,5-Dimethoxy-4-ethylphenyl) ethanamine (2C-E)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4003,"2-(2,5-Dimethoxy-4-methylphenyl) ethanamine (2C-D)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4004,"2-(2,5-Dimethoxy-4-nitro-phenyl) ethanamine (2C-N)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4005,"2-(4-Bromo-2,5-dimethoxy- phenyl)-N-(2-methoxybenzyl) ethanamine (25B-NBOMe; 2C-B-NBOMe; 25B; Cimbi-36)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4006,"2-(4-Chloro-2,5-dimethoxy- phenyl)-N-(2-methoxybenzyl) ethanamine (25C-NBOMe; 2C-C- NBOMe; 25C; Cimbi-82)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4007,"2-(4-Chloro-2,5-dimethoxyphenyl) ethanamine (2C-C)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4008,"2-(4-Ethylthio-2,5-dimethoxy- phenyl) ethanamine (2C-T-2)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4009,"2-(4-Iodo-2,5-dimethoxyphenyl) ethanamine (2C-I)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4010,"2-(4-Iodo-2,5-dimethoxyphenyl)-N- (2-methoxybenzyl) ethanamine (25I-NBOMe; 2C-I-NBOMe; 25I)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4011,"2-(4-Isopropylthio)-2,5- dimethoxyphenyl) ethanamine (2C-T-4)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4012,"2, 5- Dimethoxy-4-ethylamphetamine",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4013,"2, 5- Dimethoxyamphetamine",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4014,"2, 5-Dimethoxy-4-(n)-propylthiophenethylamine (2C-T-7)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4015,"2,5-dimethoxy-4-methylamphetamine (DOM)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4016,"2,5-dimethoxyphenethyl- amine (25H-NBOMe; 25H; 2C-H-NBOMe; 2C-H)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4017,"3,4-Methylenedioxyamphetamine (Methylenedioxyamphetamine; MDA)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4018,"3,4-Methylenedioxymethamphetamine (Methylenedioxy-methamphetamine; MDMA)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4019,3-MeO-PCP (3-methoxy-phencyclidine),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4020,"3-methoxy-4, 5-methylenedioxyamphetamine (MMDA; 5- methoxy-MDA)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4021,"3-methoxy-4,5-methylenedioxymethamphetamine (MMDMA; 5-methoxy-MDMA)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4022,"4- Bromo-2,5-dimethoxyphenethylamine (Bromodimethoxy- phenethylamine; 2C-B)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4023,"4-Bromo-2,5-dimethoxyamphetamine (Bromo-dimethoxyamphetamine; 4-bromo-DMA)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4024,4-MeO-PCP (4-methoxy-phencyclidine),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4025,4-Methoxyamphetamine (4-MA; Para-Methoxyamphetamine; PMA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4026,"5,6-methylenedioxy-2-aminoindane (MDAI)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4027,5-iodo-2-aminoindane (5-IAI),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4028,5-methoxy-dimethyltryptamine (5-MeO-DMT),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4029,"5-methoxy-N,N-diisopropyltryptamine (5-MeO-DiPT)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4030,5-methoxy-N-methyl-N-isopropyltryptamine (5-MeO-MiPT),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4031,"8-bromo-2,3,6,7-benzo-dihydro-difuran-ethylamine (2C-B-FLY)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4032,Alpha-Ethyltryptamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4033,Alpha-methyltryptamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4034,Aminopropyl benzofuran (APB),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4035,Aminopropyl dihydryobenzofuran (APDB),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4036,Benzodioxolylbutanamine (BDB),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4037,Bufotenine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4038,Diethyltryptamine (DET),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4039,Dimethoxyamphetamine (DMA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4040,Dimethoxyethylamphetamine; (DOET),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4041,Dimethylone (bk-MDDMA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4042,Dimethyltryptamine (DMT),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4043,"Ethylone (3,4-methylenedioxy-N-ethylcathinone; bk-MDEA)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4044,Ibogaine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4045,Lysergic Acid Amide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4046,Lysergic Acid Diethylamide (LSD),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4047,Mescaline (Peyote),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4048,Methoxetamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4049,"Methoxyamphetamine (4-MA, 4-Methoxyamphetamine, Para-Methoxyamphetamine (PMA))",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4050,"Methoxy-N, N-disopropyltryptamine (5-MeO-DiPT; Foxy; Foxy-methoxy)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4051,Methoxyphenidine (MXP),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4052,Methylaminopropyl benzofuran (MAPB),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4053,Methylaminorex,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4054,Methylbenzodioxolylbutanamine (MBDB),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4055,Methylenedioxy-N-ethylamphetamine (MDEA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4056,"N,N-diallyl-5-methoxytryptamine (5-MeO-DALT)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4057,Nabilone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4058,N-Ethyl-1-phenylcyclohexylamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4059,N-Ethyl-3piperdyl benzilate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4060,N-Hydroxymethylenedioxy-amphetamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4061,N-Methylpiperidyl benzilate,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4062,Norketamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4063,para-methyoxy-N-methylamphetamine (PMMA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4064,Psilocin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4065,Psilocybin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4066,Psilocyn,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4067,Salvinorin B,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4068,Trimethoxy amphetamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",4997,"Hallucinogen, Type Unknown",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5001,"(Synthetic Cannabinoid) 4-CN-CUMYL-BINACA (4-cyano-CUMYL-BINACA, CUMYL-CYBINACA, SGT-78)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5002,(Synthetic Cannabinoid) 5F-AB-001,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5003,(Synthetic Cannabinoid) 5F-ADB,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5004,"(Synthetic Cannabinoid) 5F-ADB (5F-MDMB-PINACA, 5-fluoro-MDMB-PINACA)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5005,(Synthetic Cannabinoid) 5F-ADBICA (5F-ADB-PICA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5006,(Synthetic Cannabinoid) 5F-ADB-PINACA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5007,"(Synthetic Cannabinoid) 5F-AEB (5F-EMB-PINACA, 5-fluoro-EMB-PINACA)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5008,"(Synthetic Cannabinoid) 5F-AMB (5F-MMB-PINACA, 5-fluoro-MMB-PINACA, 5F-AMB-PINACA)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5009,(Synthetic Cannabinoid) 5F-APINACA (5F-AKB-48),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5010,(Synthetic Cannabinoid) 5F-APP-PICA (PX-1),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5011,(Synthetic Cannabinoid) 5F-APP-PINACA (PX-2),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5012,(Synthetic Cannabinoid) 5F-EDMB-PINACA (5-fluoro-EDMB-PINACA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5013,(Synthetic Cannabinoid) 5F-MDMB-PICA (5-fluoro-MDMB-PICA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5014,(Synthetic Cannabinoid) 5F-MN-18,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5015,(Synthetic Cannabinoid) 5F-NA-PIC (5-fluoro-NA-PIC),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5016,(Synthetic Cannabinoid) 5F-PB-22,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5017,"(Synthetic Cannabinoid) 5F-QU-PINAC (5-fluoro-QU-PINAC, 5F-NPB-22)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5018,(Synthetic Cannabinoid) AB-CHMINACA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5019,(Synthetic Cannabinoid) AB-FUBINACA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5020,(Synthetic Cannabinoid) AB-PINACA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5021,(Synthetic Cannabinoid) ADB-CHMINACA (ADMB-CHMINACA; MAB-CHMINACA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5022,(Synthetic Cannabinoid) ADB-FUBICA (ADMB-FUBICA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5023,(Synthetic Cannabinoid) ADB-FUBINACA (ADMB-FUBINACA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5024,(Synthetic Cannabinoid) ADBICA (ADB-PICA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5025,(Synthetic Cannabinoid) ADB-PINACA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5026,(Synthetic Cannabinoid) AM-2201,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5027,(Synthetic Cannabinoid) AMB,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5028,(Synthetic Cannabinoid) AMB-CHMINACA (MMB-CHMINACA; MA-CHMINACA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5029,(Synthetic Cannabinoid) AMB-FUBINACA (FUB-AMB; MMB-FUBINACA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5030,(Synthetic Cannabinoid) APICA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5031,(Synthetic Cannabinoid) APP-CHMINACA (PX-3),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5032,(Synthetic Cannabinoid) BB-22 (QUCHIC),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5033,(Synthetic Cannabinoid) CUMYL-THPINACA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5034,(Synthetic Cannabinoid) EG-2201,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5035,(Synthetic Cannabinoid) EMB-FUBINACA (FUB-AEB; AEB-FUBINACA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5036,(Synthetic Cannabinoid) FDU-PB-22,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5037,(Synthetic Cannabinoid) FUB-144,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5038,(Synthetic Cannabinoid) FUB-APINACA (FUB-AKB48; ADAMANTYL-FUBINACA ),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5039,(Synthetic Cannabinoid) FUBIMINA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5040,(Synthetic Cannabinoid) FUB-JWH-018,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5041,(Synthetic Cannabinoid) JWH-018,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5042,(Synthetic Cannabinoid) JWH-122,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5043,(Synthetic Cannabinoid) MDMB-CHMCZCA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5044,(Synthetic Cannabinoid) MDMB-CHMICA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5045,(Synthetic Cannabinoid) MDMB-CHMINACA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5046,(Synthetic Cannabinoid) MDMB-FUBICA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5047,(Synthetic Cannabinoid) MDMB-FUBINACA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5048,(Synthetic Cannabinoid) MMB-FUBICA (AMB-FUBICA),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5049,(Synthetic Cannabinoid) MN-18,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5050,(Synthetic Cannabinoid) MN-25,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5051,(Synthetic Cannabinoid) MO-CHMINACA,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5052,(Synthetic Cannabinoid) NM-2201,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5053,(Synthetic Cannabinoid) PB-22 (QUPIC),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5054,(Synthetic Cannabinoid) PX1,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5055,(Synthetic Cannabinoid) PX2,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5056,(Synthetic Cannabinoid) THJ-018,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5057,(Synthetic Cannabinoid) THJ-2201,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5058,(Synthetic Cannabinoid) UR-144,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5059,(Synthetic Cannabinoid) XLR-11,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5060,Delta 9-tetrahydrocannabinol [THC],NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5061,Dronabinol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5062,11-nor-9-carboxy-delta-9- tetrahydrocannabinol (Carboxy THC),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5063,11-hydroxy-delta-9-tetrahydrocannabinol (Hydroxy-THC),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5065,Cannabidiol [CBD],NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5997,"Cannabinoid, Type Unknown",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",6001,Ketamine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",6002,Phencyclidine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",6003,Phenylcyclohexyl-Pyrrolidine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",6004,"Pyrrolidine (PCPy, PHP, TCPy)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",6005,Etomidate [Amidate],NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",6997,"Dissociative Anesthetic, Type Unknown",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",7001,"1,1-Difluoroethane (Diflouroethane, DFE)",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",7002,Amyl Nitrite,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",7003,Butyl Nitrite,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",7004,Cyclohexl Nitrite,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",7005,Enflurane,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",7006,Ether,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",7007,Halothane,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",7008,Nitrous Oxide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",7009,Tetrafluoroethane,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",7010,Toluene,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",7011,Trichlorotrifluoroethane (Freon),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",7012,Chloroform (trichloromethane),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",7997,"Inhalant, Type Unknown",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8001,Boldenone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8002,Chlorotestosterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8003,Dehydrochloromethyltestosterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8004,Dihydrotestosterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8005,Drostanolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8006,Ethylestrenol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8007,Fluoxymesterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8008,Formebulone (Formebolone),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8009,Mesterolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8010,Methandienone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8011,Methandranone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8012,Methandriol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8013,Methandrostenolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8014,Methenolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8015,Methyltestosterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8016,Mibolerone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8017,Nandrolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8018,Norethandrolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8019,Oxandrolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8020,Oxymesterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8021,Oxymetholone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8022,Stanolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8023,Stanozolol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8024,Testolactone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8025,Testosterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8026,Trenbolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8027,Clostebol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8028,"Alpha, Beta-dihydroxy-alpha-androstane",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8029,Alpha-methyl-alpha-beta-dihydroxy-alpha-androstane,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8030,Alpha-methyl-beta-beta-dihydroxy-alpha-androstane,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8031,Alpha-methyl-beta-beta-dihydroxy-androstene,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8032,Alpha-methyl-delta 1-dihydrotestosterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8033,Alpha-methyl-hydroxynandrolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8034,Androstanedione,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8035,Androstenediol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8036,Androstenedione,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8037,"Beta, beta-dihydroxy-alpha-androstane",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8038,Bolasterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8039,Calusterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8040,Delta 1-dihydrotestosterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8041,Furazabol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8042,Hydroxy-Nortestosterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8043,Hydroxytestosterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8044,Mestanolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8045,Methyldienolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8046,Methyltrienolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8047,Norandrostenediol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8048,Norandrostenedione,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8049,Norbolethone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8050,Norclostebol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8051,Normethandrolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8052,Stenbolone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8053,Tetrahydrogestrinone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8054,Boldione,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8055,Desoxymethyltestosterone,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8056,Dienedione,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",8997,"Anabolic Steroid, Type Unknown",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9001,6-beta-naltrexol (naltrexone metabolite),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9002,Acetaminophen (OTC ANALGESIC),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9003,Benzocaine (TOPICAL FOR PAIN),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9004,Chlorpropamide-(FOR DIABETES),NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9005,Cimetidine -(FOR ULCERS/GERD),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9006,Desloratadine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9007,Diltiazem,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9008,Ergotamine-VASOCONSTRICTOR,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9009,Fexofenadine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9010,Fluconazole,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9011,Hydrochlorothiazide,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9012,Hydroxychloroquine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9013,Ibuprofen - (OTC ANALGESIC),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9014,Ketoprofen (ANALGESIC),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9015,Ketorolac (Toradol),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9016,Labetalol,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9017,Levamisole (CUTTING AGENT FOR COCAINE / VET. DEWORMING AGENT),NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9018,Lidocaine (ANESTHETIC),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9019,Loratadine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9020,Meta-Chlorophenylpiperazine (mCPP) (TRAZODONE METABOLITE),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9021,Naloxone - (OPIOID ANTAGONIST),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9022,Naltrexone - (OPIOID ANTAGONIST),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9023,Naproxen - (OTC ANALGESIC),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9024,Phenazone (Antipyrene) (ANALGESIC),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9026,Salicylic Acid (Salicylate)-(OTC ANALGESIC),NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9027,Theobromine (in chocolate),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9028,Theophylline-(for asthma),NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9029,Amlodipine,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9030,Metformin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9031,Atorvastatin,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9032,Warfarin [Coumadin],NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9995,Not Reported,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9996,Other Drug (Specify:),NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9997,"Tested for Drugs, Results Unknown",NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9998,"Tested for Drugs, Drugs Found, Type Unknown/Positive",NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9999,Reported as Unknown if Tested for Drugs,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",0,None Noted,NA,NA,NA,NA,NA,NA,NA,NA,1,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",NA,Reported as Unknown*/,NA,NA,NA,NA,NA,NA,NA,NA,1,NA
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,0,Not Signed,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,4,County,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,5,Township,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,6,Municipal,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,10,Parkway Marker or Forest Route Marker [Specify:],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,11,Off-Interstate Business Marker,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,12,Secondary Route,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,13,Bureau of Indian Affairs,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,95,Other,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,96,Trafficway Not in State Inventory,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,ROUTE,route,Route Signing,This data element identifies the route signing designation of the trafficway on which the crash occurred.,Prior to 2015 the Data Element ID was C12.,99,Unknown/Not Reported,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,RUR_URB,rur_urb,Rural Urban Classification,This data element identifies the classification of the segment of the trafficway on which the crash occurred based on FHWA-approved adjusted Census boundaries of small urban and urbanized areas.,From 1975 to 1986 there was a similar Land Use (LAND_USE) data element. From 1987 to 2014 urban and rural classifications can be obtained from the data element Roadway Function Class. Prior to 2023 this data element’s name was “Land Use.”,1,Rural,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,RUR_URB,rur_urb,Rural Urban Classification,This data element identifies the classification of the segment of the trafficway on which the crash occurred based on FHWA-approved adjusted Census boundaries of small urban and urbanized areas.,From 1975 to 1986 there was a similar Land Use (LAND_USE) data element. From 1987 to 2014 urban and rural classifications can be obtained from the data element Roadway Function Class. Prior to 2023 this data element’s name was “Land Use.”,2,Urban,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,RUR_URB,rur_urb,Rural Urban Classification,This data element identifies the classification of the segment of the trafficway on which the crash occurred based on FHWA-approved adjusted Census boundaries of small urban and urbanized areas.,From 1975 to 1986 there was a similar Land Use (LAND_USE) data element. From 1987 to 2014 urban and rural classifications can be obtained from the data element Roadway Function Class. Prior to 2023 this data element’s name was “Land Use.”,6,Trafficway Not in State Inventory,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,RUR_URB,rur_urb,Rural Urban Classification,This data element identifies the classification of the segment of the trafficway on which the crash occurred based on FHWA-approved adjusted Census boundaries of small urban and urbanized areas.,From 1975 to 1986 there was a similar Land Use (LAND_USE) data element. From 1987 to 2014 urban and rural classifications can be obtained from the data element Roadway Function Class. Prior to 2023 this data element’s name was “Land Use.”,8,Not Reported,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,RUR_URB,rur_urb,Rural Urban Classification,This data element identifies the classification of the segment of the trafficway on which the crash occurred based on FHWA-approved adjusted Census boundaries of small urban and urbanized areas.,From 1975 to 1986 there was a similar Land Use (LAND_USE) data element. From 1987 to 2014 urban and rural classifications can be obtained from the data element Roadway Function Class. Prior to 2023 this data element’s name was “Land Use.”,9,Unknown,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,FUNC_SYS,func_sys,Functional System,NA,NA,2,Other Freeways and Expressways,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,FUNC_SYS,func_sys,Functional System,NA,NA,3,Other Principal Arterial,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,26,Private (Other Than Railroad),NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,RD_OWNER,rd_owner,Ownership,NA,NA,95,Other [Specify:],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,NHS,nhs,National Highway System,This data element identifies whether this crash occurred on a trafficway that is part of the National Highway System.,Prior to 2015 the Data Element ID was C10.,0,This Section IS NOT on the NHS,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,NHS,nhs,National Highway System,This data element identifies whether this crash occurred on a trafficway that is part of the National Highway System.,Prior to 2015 the Data Element ID was C10.,1,This Section IS ON the NHS,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,NHS,nhs,National Highway System,This data element identifies whether this crash occurred on a trafficway that is part of the National Highway System.,Prior to 2015 the Data Element ID was C10.,9,Unknown if This Section Is on the NHS,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,RELJCT1,reljct1,Relation to Junction - Within Interchange Area,This data element identifies the crash’s location with respect to presence in an interchange area. The coding of this data element is done in two sub-fields (see also C20B) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20A.,0,No,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,RELJCT1,reljct1,Relation to Junction - Within Interchange Area,This data element identifies the crash’s location with respect to presence in an interchange area. The coding of this data element is done in two sub-fields (see also C20B) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20A.,1,Yes,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,RELJCT1,reljct1,Relation to Junction - Within Interchange Area,This data element identifies the crash’s location with respect to presence in an interchange area. The coding of this data element is done in two sub-fields (see also C20B) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20A.,8,Not Reported,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,accident,RELJCT1,reljct1,Relation to Junction - Within Interchange Area,This data element identifies the crash’s location with respect to presence in an interchange area. The coding of this data element is done in two sub-fields (see also C20B) and is based on the location of the “First Harmful Event” of the crash.,Prior to 2015 the Data Element ID was C20A.,9,Reported as Unknown,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,SPEC_USE,spec_use,Special Use,This data element identifies any special use associated with this vehicle at the time of the crash.,Prior to 2016 the Data Element ID was V22. From 2016 to 2019 the Data Element ID was V23. This data element also appears in the Person data file set and in the Parkwork data file as PSP_USE.,0,NA,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ROLLOVER,rollover,Rollover,This data element identifies this vehicle’s involvement in a rollover or overturn during the crash. Rollover is defined as any vehicle rotation of 90° or more about any true longitudinal or lateral axis. Rollover can occur at any time during the crash.,Data are not available from 1975 to 1977. Prior to 2016 the Data Element ID was V26. From 2016 to 2019 the Data Element ID was V27. Starting in 2022 this data element is derived from the “Sequence of Events” data element for each vehicle with an event equal to 01. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. This data element also appears in the Person data file.,0,No Rollover,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ROLLOVER,rollover,Rollover,This data element identifies this vehicle’s involvement in a rollover or overturn during the crash. Rollover is defined as any vehicle rotation of 90° or more about any true longitudinal or lateral axis. Rollover can occur at any time during the crash.,Data are not available from 1975 to 1977. Prior to 2016 the Data Element ID was V26. From 2016 to 2019 the Data Element ID was V27. Starting in 2022 this data element is derived from the “Sequence of Events” data element for each vehicle with an event equal to 01. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. This data element also appears in the Person data file.,3,Rollover,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ROLLOVER,rollover,Rollover,This data element identifies this vehicle’s involvement in a rollover or overturn during the crash. Rollover is defined as any vehicle rotation of 90° or more about any true longitudinal or lateral axis. Rollover can occur at any time during the crash.,Data are not available from 1975 to 1977. Prior to 2016 the Data Element ID was V26. From 2016 to 2019 the Data Element ID was V27. Starting in 2022 this data element is derived from the “Sequence of Events” data element for each vehicle with an event equal to 01. See Appendix B: Rules for Derived Data Elements for an explanation of this data element and how it is derived. This data element also appears in the Person data file.,8,Not Applicable,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",7884,Dodge Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",19898,Cadillac Other (medium/heavy truck),NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",20884,Chevrolet Medium/Heavy - Unknown engine location,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",55882,Hyundai Medium/Heavy Trucks - COE (low entry),NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,MAK_MOD,mak_mod,NCSA Make Model Combined,"This derived data element represents the five-digit combination of two data elements, the two- digit “NCSA Make” code (MAKE) followed by the three-digit “NCSA Model” code (MODEL).","Prior to 2020 this data element’s name was ""Make Model Combined."" This data element also appears in the Person data file and in the Parkwork data file as PMAK_MOD.",73707,Kawasaki Electric Motorcycle,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,L_STATE,l_state,Driver License State,This element identifies the State of issue for the license held by this driver.,NA,57,NA,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,CDL_STAT,cdl_stat,Commercial MV License Status,This data element indicates the status of the driver’s commercial driver’s license (CDL) if applicable.,"Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.).",7,NA,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,FIRST_YR,first_yr,"Date of Oldest Crash, Suspension or Conviction (Year)","This data element records the year of the first crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of First Crash, Suspension, or Conviction.""",2023,2023,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,LAST_YR,last_yr,"Date of Most Recent Crash, Suspension or Conviction (Year)","This data element records the year of the last crash, suspension, or conviction for this driver that occurred within 5 years of the crash date.","Prior to 2011, if no driver was present or the driver presence was unknown, then this data element was left blank. In SAS these blank values are represented by a single dot or period (.). Prior to 2015 the time frame for this data element was any occurrence within 3 years of the crash date. Prior to 2020 this data element’s name was ""Year of Last Crash, Suspension, or Conviction.""",2023,2023,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,68,"J68-Changing Trafficway, Vehicle Turning-Turn Across Path-Initial Opposite Directions (Left/Right)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,69,"J69-Changing Trafficway, Vehicle Turning-Turn Across Path-Initial Opposite Directions (Going Straight)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,70,"J70-Changing Trafficway, Vehicle Turning-Turn Across Path-Initial Same Directions (Turning Right)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,71,"J71-Changing Trafficway, Vehicle Turning-Turn Across Path-Initial Same Directions (Going Straight)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,72,"J72-Changing Trafficway, Vehicle Turning-Turn Across Path-Initial Same Directions (Turning Left)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,73,"J73-Changing Trafficway, Vehicle Turning-Turn Across Path-Initial Same Directions (Going Straight)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,74,"J74-Changing Trafficway, Vehicle Turning-Turn Across Path-Specifics Other",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,75,"J75-Changing Trafficway, Vehicle Turning-Turn Across Path-Specifics Unknown",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,76,"K76-Changing Trafficway, Vehicle Turning-Turn Into Path-Turn Into Same Direction (Turning Left)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,77,"K77-Changing Trafficway, Vehicle Turning-Turn Into Path-Turn Into Same Direction (Going Straight)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,78,"K78-Changing Trafficway, Vehicle Turning-Turn Into Path-Turn Into Same Direction (Turning Right)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,79,"K79-Changing Trafficway, Vehicle Turning-Turn Into Path-Turn Into Same Direction (Going Straight)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,80,"K80-Changing Trafficway, Vehicle Turning-Turn Into Path-Turn Into Opposite Directions (Turning Right)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,81,"K81-Changing Trafficway, Vehicle Turning-Turn Into Path-Turn Into Opposite Directions (Going Straight)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,82,"K82-Changing Trafficway, Vehicle Turning-Turn Into Path-Turn Into Opposite Directions (Turning Left)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,83,"K83-Changing Trafficway, Vehicle Turning-Turn Into Path-Turn Into Opposite Directions (Going Straight)",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,84,"K84-Changing Trafficway, Vehicle Turning-Turn Into Path-Specifics Other",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_TYPE,acc_type,Crash Type,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,85,"K85-Changing Trafficway, Vehicle Turning-Turn Into Path-Specifics Unknown",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,0,No Impact,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,101,Single Driver-Right Roadside Departure,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,102,Single Driver-Left Roadside Departure,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,103,Single Driver-Struck Object While Moving Forward,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,201,"Same Trafficway, Same Direction-Rear End, Trailing Vehicle",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,202,"Same Trafficway, Same Direction-Rear End, Lead Vehicle",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,203,"Same Trafficway, Same Direction-Rear End, Other or Unknown",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,204,"Same Trafficway, Same Direction-Forward Impact, Frontal Impact After Maneuver",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,205,"Same Trafficway, Same Direction-Forward Impact, Rear End Impact After Maneuver",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,206,"Same Trafficway, Same Direction-Forward Impact, Other or Unknown",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,207,"Same Trafficway, Same Direction-Sideswipe, Angle, Vehicle on Left",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,208,"Same Trafficway, Same Direction-Sideswipe, Angle, Vehicle on Right",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,209,"Same Trafficway, Same Direction-Sideswipe, Angle, Other or Unknown",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,301,"Same Trafficway, Opposite Direction-Lateral Move [Left/Right], Head-On, Sideswipe, or Angle",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,302,"Same Trafficway, Opposite Direction-Lateral Move [Going Straight], Head-On, Sideswipe, or Angle",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,303,"Same Trafficway, Opposite Direction-Lateral Move, Other or Unknown",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,304,"Same Trafficway, Opposite Direction-Forward Impact After Maneuver, Departed Lane",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,305,"Same Trafficway, Opposite Direction-Forward Impact After Maneuver, Remained in Lane",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,306,"Same Trafficway, Opposite Direction-Forward Impact After Maneuver, Other or Unknown",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,401,"Changing Trafficway, Vehicle Turning-Turn Across Path, Initial Opposite Directions [Left/Right]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,402,"Changing Trafficway, Vehicle Turning-Turn Across Path, Initial Opposite Directions [Going Straight]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,403,"Changing Trafficway, Vehicle Turning-Turn Across Path, Initial Same Directions [Turning Right]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,404,"Changing Trafficway, Vehicle Turning-Turn Across Path, Initial Same Directions [Going Straight, Other Vehicle Turning Right]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,405,"Changing Trafficway, Vehicle Turning-Turn Across Path, Initial Same Directions [Turning Left]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,406,"Changing Trafficway, Vehicle Turning-Turn Across Path, Initial Same Directions [Going Straight, Other Vehicle Turning Left]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,407,"Changing Trafficway, Vehicle Turning-Turn Across Path, Other or Unknown",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,408,"Changing Trafficway, Vehicle Turning-Turn Into Path, Turn into Same Direction [Turning Left]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,409,"Changing Trafficway, Vehicle Turning-Turn Into Path, Turn into Same Direction [Going Straight, Other Vehicle Turning Left]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,410,"Changing Trafficway, Vehicle Turning-Turn Into Path, Turn into Same Direction [Turning Right]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,411,"Changing Trafficway, Vehicle Turning-Turn Into Path, Turn into Same Direction [Going Straight, Other Vehicle Turning Right]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,412,"Changing Trafficway, Vehicle Turning-Turn Into Path, Turn into Opposite Directions [Turning Right]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,413,"Changing Trafficway, Vehicle Turning-Turn Into Path, Turn into Opposite Directions [Going Straight, Other Vehicle Turning Right]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,414,"Changing Trafficway, Vehicle Turning-Turn Into Path, Turn into Opposite Directions [Turning Left]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,415,"Changing Trafficway, Vehicle Turning-Turn Into Path, Turn into Opposite Directions [Going Straight, Other Vehicle Turning Left]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,416,"Changing Trafficway, Vehicle Turning-Turn into Path, Other or Unknown",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,501,"Intersecting Paths-Straight Paths, Striking from the Right",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,502,"Intersecting Paths-Straight Paths, Struck on the Right",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,503,"Intersecting Paths-Straight Paths, Striking from the Left",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,504,"Intersecting Paths-Straight Paths, Struck on the Left",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,505,"Intersecting Paths-Straight Paths, Other or Unknown",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,992,Backing Vehicle,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,993,Other Vehicle,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,998,Other Crash Type,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehicle,ACC_CONFIG,acc_config,Crash Type Configuration,This data element identifies the attribute that best describes the type of crash this vehicle was involved in based on the “First Harmful Event” and the precrash circumstances. For graphic descriptions of possible values see Appendix A: PC23 Crash Type Configuration Diagram.,In 2023 the data element CRASH TYPE was condensed and renamed CRASH TYPE CONFIGURATION in an effort to simplify data collection. What were previously “Configurations” were generally appended to the labels of the individual CRASH TYPE CONFIGURATION attributes to make analysis with prior years easier. For graphic descriptions of possible values from 2016 to 2022 see Appendix A: PC23 Crash Type Diagram.,999,Unknown Crash Type,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2023,2023,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,person,DEATH_YR,death_yr,Death Date (Year),This data element records the year of this person’s death.,"A person can die the year after the crash year. Prior to 2019 the Data Element ID was P24C/NM23C. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa. Prior to 2022 the Data Element ID was P24C/NM24C.",2024,2024,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",102,Aggressive Driving by Non-Contact Vehicle Driver,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,crashrf,CRASHRF,crashrf,Crash Related Factor,This data element records factors related to the crash expressed in the case material.,"There are also vehicle related factors in the Vehiclesf and Pvehiclesf data files, driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element was collected at the Crash level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Accident Data Elements at the end of the Accident Data File section. Refer to the discontinued element for a history of this data element’s attributes.",103,Road Rage by Non-Contact Vehicle Driver,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,vehiclesf,VEHICLESF,vehiclesf,Vehicle Related Factor,This data element records factors related to this motor vehicle in-transport expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Pvehiclesf data file (for parked/working vehicles), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Pre-existing vehicle defects are captured in the data element “Contributing Circumstances, Motor Vehicle” (Factor.MFACTOR). Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",32,NA,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,pvehiclesf,PVEHICLESF,pvehiclesf,Vehicle Related Factor,This data element records factors related to this parked/working motor vehicle expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf data file (for motor vehicles in-transport), driver related factors in the Driverrf data file, and person related factors in the Personrf data file. Prior to 2020 this data element’s ID was V36 and it was collected at the Vehicle level with up to two factors being selected. These two elements were discontinued and moved to the Discontinued Parkwork Data Elements at the end of the Parkwork Data File section. Refer to the discontinued element for a history of this data element’s attributes.",32,NA,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",100,Using a Belt-Positioning Device or Other,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",102,Aggressive Driving,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",103,Road Rage,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",104,Police Pursuing This Driver,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,driverrf,DRIVERRF,driverrf,Driver Related Factor,This data element records factors related to this driver expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and person related factors in the Personrf data file. Person related factors are all set to 0 for drivers. Prior to 2020 this data element was collected at the Vehicle level and up to four factors could be selected. These four elements were discontinued and moved to the Discontinued Vehicle Data Elements at the end of the Vehicle Data File section. Refer to the discontinued element for a history of this data element’s attributes.",105,Police Officer in Pursuit,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,pbtype,BIKECTYPE,bikectype,Bicyclist Crash Type,This data element summarizes the circumstances of the crash for this bicyclist.,This data element is applicable to bicyclists only. Prior to 2022 the Element Data ID was NM9- PB30B.,231,NA,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",1,Going To or From School [Pre-K-12],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",8,"In Roadway - Other [Working, Playing, Etc.]",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,nmprior,NMACTION,nmaction,Non-Motorist Action/Circumstances,This data element describes the actions of the non-motorist immediately prior to their involvement in the crash.,"Some information that had been collected under “Related Factors—Person Level” are now captured under this new data element. Please note the ""non-motorist"" may include people in motor vehicles not in-transport, however this data element is only collected for people who are not occupants of motor vehicles. Prior to 2014 this data element’s name was “Non-Motorist Action/Circumstances Prior to Crash.” Prior to 2022 the Element Data ID was NM11.",10,Working in Trafficway [Incident Response],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,0,Test Not Given,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,1,Enzyme-Linked Immunosorbent Assay [ELISA],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,2,Enzyme-Multiplied Immunoassay Technique [EMIT],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,3,Liquid Chromatography/Tandem Mass Spectrometry [LC/MS-MS],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,4,Headspace Gas Chromatography [HS/GC],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,5,NA,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,6,Enzyme Immunoassay [EIA],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,8,Other Screening Test Method [Specify:],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,9,Unknown Screening Test Method,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,11,High-Performance Liquid Chromatography [HPLC],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,12,Liquid Chromatography/Mass Spectrometry [LC/MS],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,13,Liquid Chromatography/Time of Flight - Mass Spectrometry [LC/TOF - MS],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,14,Gas Chromatography and Mass Spectrometry [GC/MS],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,15,Gas Chromatography [GC],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,16,Liquid Chromatography- Tandem Mass Spectrometry [LC/MS-MS],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,17,Liquid Chromatography/Time of Flight - Tandem Mass Spectrometry [LC/TOF-MS/MS],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,18,Other Confirmatory Test Method [Specify:],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,19,Unknown Confirmatory Test Method,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,20,Quadrupole Time of Flight [QTOF],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,21,Liquid Chromatography/Quadrupole Time of Flight [LC/QTOF],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,22,Quadrupole Time of Flight Mass Spectrometry [QTOF MS],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,23,Gas Chromatography and Tandem Mass Spectrometry [GC/MS-MS],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,24,Headspace Gas Chromatography [HS-GC],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,25,Gas Chromatography With Flame Ionization Detection [GC FID],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,26,Headspace Gas Chromatography with Flame Ionization Detection [HS-GC FID],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,96,Not Reported,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,97,Unknown Testing Method,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGMETHOD,drugmethod,Drug Testing Method,This data element records the testing methodology used to detect the likely presence of drugs and to confirm specific drugs and quantities in the drug specimen.,There are two primary categories of drug testing methods employed for drug detection: screening and confirmatory. Some drug testing methods can be used as both a screening and confirmatory testing method.,99,Reported as Unknown if Tested,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",1,None Detected/Below Threshold,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2043,Clonidine - (FOR HIGH BLOOD PRESSURE & ADHD),NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2225,Bromazolam,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",2397,"Tricyclic Antidepressant, Type Unknown",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",3032,Cocaethylene (ethylbenzoylecgonine),NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5064,Cannabigerol [CBG],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5066,Tetrahydrocannabinolic Acid [THCA],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",5067,Cannabinol [CBN],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",6007,Propofol,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9004,Chlorpropamide - (FOR DIABETES),NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9008,Ergotamine - VASOCONSTRICTOR,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9017,Levamisole (CUTTING AGENT FOR COCAINE / VET. DEWORMING AGENT,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9026,Salicylic Acid (Salicylate) - (OTC ANALGESIC),NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9028,Theophylline - (for asthma),NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9035,Carboxyhemoglobin [Carbon Monoxide],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGRES,drugres,Drug Test Result,This data element identifies the drug test result for this person.,"Prior to 2018 this data element was in the Person data file and up to three drug results could be recorded. See ""Drug Test Result"" under the discontinued data elements of the Person Data file for details. See Specific Drug Listing in the FARS/CRSS Coding and Validation Manual. Caution should be used when interpreting Drug Test Result data. For details, please refer to the research note Understanding the Limitations of Drug Test Information, Reporting, and Testing Practices in Fatal Crashes. Prior to 2019 the Data Element ID was P21C/NM20C. From 2019-2021 the Data Element ID was P21B/NM21B. In 2022 the Element ID was P19C/NM21C. In 2022, the list of drug names was refined and expanded to more accurately reflect the dynamic advancements in pharmacology. These data are not comparable to prior years’ data. See Appendix H: Notable Changes -Modernization of Drug Toxicology Data Collection",9998,"Tested for Drugs, Drugs Detected, Type Unknown/Positive",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGQTY,drugqty,Drug Quantity, This data element records the quantitative results for the drugs reported in the Drug Test Result data element.,NA,0,Test Not Given,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGQTY,drugqty,Drug Quantity, This data element records the quantitative results for the drugs reported in the Drug Test Result data element.,NA,1,None Detected/Below Threshold,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGQTY,drugqty,Drug Quantity, This data element records the quantitative results for the drugs reported in the Drug Test Result data element.,NA,2,Actual Drug Quantity,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGQTY,drugqty,Drug Quantity, This data element records the quantitative results for the drugs reported in the Drug Test Result data element.,NA,3,Presumptive Positive,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGQTY,drugqty,Drug Quantity, This data element records the quantitative results for the drugs reported in the Drug Test Result data element.,NA,4,"Drugs Detected, Unknown Testing Method",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGQTY,drugqty,Drug Quantity, This data element records the quantitative results for the drugs reported in the Drug Test Result data element.,NA,96,Not Reported,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGQTY,drugqty,Drug Quantity, This data element records the quantitative results for the drugs reported in the Drug Test Result data element.,NA,97,"Tested for Drugs, Results Unknown",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGQTY,drugqty,Drug Quantity, This data element records the quantitative results for the drugs reported in the Drug Test Result data element.,NA,98,"Tested for Drugs, Drugs Detected, Unknown Quantity",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGQTY,drugqty,Drug Quantity, This data element records the quantitative results for the drugs reported in the Drug Test Result data element.,NA,99,Reported as Unknown if Tested,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGACTQTY,drugactqty,Actual Quantity,This subfield records the quantitative result of a chemical test for the drug identified in the Drug Test Result data element.,NA,-99,Not Applicable,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGUOM,druguom,Unit of Measure,This data element records the unit of measure for the quantity of the drug coded in the Drug Quantity data element from a confirmatory toxicology test.,NA,-9,Not Applicable,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGUOM,druguom,Unit of Measure,This data element records the unit of measure for the quantity of the drug coded in the Drug Quantity data element from a confirmatory toxicology test.,NA,1,mg/dL,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGUOM,druguom,Unit of Measure,This data element records the unit of measure for the quantity of the drug coded in the Drug Quantity data element from a confirmatory toxicology test.,NA,2,mg/L,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGUOM,druguom,Unit of Measure,This data element records the unit of measure for the quantity of the drug coded in the Drug Quantity data element from a confirmatory toxicology test.,NA,3,mcg/mL,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGUOM,druguom,Unit of Measure,This data element records the unit of measure for the quantity of the drug coded in the Drug Quantity data element from a confirmatory toxicology test.,NA,4,gm%,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGUOM,druguom,Unit of Measure,This data element records the unit of measure for the quantity of the drug coded in the Drug Quantity data element from a confirmatory toxicology test.,NA,5,ng/mL,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGUOM,druguom,Unit of Measure,This data element records the unit of measure for the quantity of the drug coded in the Drug Quantity data element from a confirmatory toxicology test.,NA,6,mcg/L,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGUOM,druguom,Unit of Measure,This data element records the unit of measure for the quantity of the drug coded in the Drug Quantity data element from a confirmatory toxicology test.,NA,7,%,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,drugs,DRUGUOM,druguom,Unit of Measure,This data element records the unit of measure for the quantity of the drug coded in the Drug Quantity data element from a confirmatory toxicology test.,NA,8,Other [Specify:],NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",0,Not a Fatality (not applicable),NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",78,"Asian or Pacific Islander, No Specific (individual) Race",NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",201,Multiple Race - White,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,race,RACE,race,Race,This data element records the race of this person from the death certificate.,"This data element is only coded for fatalities. Prior to 2019 if more than one race was listed on the death certificate or report, the race listed first was recorded; the exception is attribute 6 (Hawaiian [includes part-Hawaiian]). Attribute 6 (Hawaiian [includes part-Hawaiian]) was coded for any person listed as Hawaiian, even if another race is listed as well. This data element is only coded for fatalities. Prior to 2019 only one attribute was coded for race and this element was stored in the Person data file. In 2019 Iowa entered this data using sources other than the official death certificate. In 2020 Iowa FARS analysts regained access to and entered official death certificate data. However, in compliance with Iowa’s State Confidentiality Policy, death certificate data cannot be disclosed or re-released to the public. Therefore, starting in 2020, all data fields with death certificate-related data for Iowa will be redacted. For more information go to Redacted Death Certificate-Related Data in Iowa.",298,Multiple Race - Other Races,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",56,NA,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",82,NA,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",102,Motor Vehicle Occupant in Prior Crash,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",103,Road Rage,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",104,Using a Belt-Positioning Device or Other,NA,NA,NA,NA,NA,NA,NA,NA,NA,1
FARS,personrf,PERSONRF,personrf,Person Related Factor,This data element records factors related to motor vehicle occupants (other than drivers) and people not in motor vehicles as expressed in the case material.,"There are also crash related factors in the Crashrf data file, vehicle related factors in the Vehiclesf and Pvehiclesf data files, and driver related factors in the Driverrf data file. Person Related Factors are all set to 0 for drivers. Attribute with a single asterisk (*) are only applicable to occupants (other than drivers) of motor vehicles. Attribute with a double asterisk (**) are only applicable to people not in motor vehicles. Prior to 2020 this data element was collected at the Person level and up to three factors could be selected. These three elements were discontinued and moved to the Discontinued Person Data Elements at the end of the Person Data File section. Refer to the discontinued element for a history of this data element’s attributes. Prior to 2022 the Data Element ID was P26/NM26.",105,Paraplegic or in a Wheelchair,NA,NA,NA,NA,NA,NA,NA,NA,NA,1